Commit 329844ee authored by Annie Sullivan's avatar Annie Sullivan Committed by Commit Bot

Update LongestInput(Timestamp|Delay)3->4

This had been missed when updating FirstInputDelay over the summer.

Change-Id: I9f635708265c009b4e89d1152c3388a499a78858
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1834116Reviewed-by: default avatarBryan McQuade <bmcquade@chromium.org>
Commit-Queue: Annie Sullivan <sullivan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#702005}
parent 6836cfc5
......@@ -120,9 +120,9 @@ const char kHistogramFirstInputDelaySkipFilteringComparison[] =
const char kHistogramFirstInputTimestampSkipFilteringComparison[] =
"PageLoad.InteractiveTiming.FirstInputTimestamp.SkipFilteringComparison";
const char kHistogramLongestInputDelay[] =
"PageLoad.InteractiveTiming.LongestInputDelay3";
"PageLoad.InteractiveTiming.LongestInputDelay4";
const char kHistogramLongestInputTimestamp[] =
"PageLoad.InteractiveTiming.LongestInputTimestamp3";
"PageLoad.InteractiveTiming.LongestInputTimestamp4";
const char kHistogramParseStartToFirstMeaningfulPaint[] =
"PageLoad.Experimental.PaintTiming.ParseStartToFirstMeaningfulPaint";
const char kHistogramParseStartToFirstContentfulPaint[] =
......
......@@ -378,13 +378,13 @@ void UkmPageLoadMetricsObserver::RecordTimingMetrics(
if (timing.interactive_timing->longest_input_delay) {
base::TimeDelta longest_input_delay =
timing.interactive_timing->longest_input_delay.value();
builder.SetInteractiveTiming_LongestInputDelay3(
builder.SetInteractiveTiming_LongestInputDelay4(
longest_input_delay.InMilliseconds());
}
if (timing.interactive_timing->longest_input_timestamp) {
base::TimeDelta longest_input_timestamp =
timing.interactive_timing->longest_input_timestamp.value();
builder.SetInteractiveTiming_LongestInputTimestamp3(
builder.SetInteractiveTiming_LongestInputTimestamp4(
longest_input_timestamp.InMilliseconds());
}
......
......@@ -863,11 +863,11 @@ TEST_F(UkmPageLoadMetricsObserverTest, LongestInputDelayAndTimestamp) {
test_ukm_recorder().ExpectEntrySourceHasUrl(kv.second.get(),
GURL(kTestUrl1));
test_ukm_recorder().ExpectEntryMetric(
kv.second.get(), PageLoad::kInteractiveTiming_LongestInputDelay3Name,
kv.second.get(), PageLoad::kInteractiveTiming_LongestInputDelay4Name,
50);
test_ukm_recorder().ExpectEntryMetric(
kv.second.get(),
PageLoad::kInteractiveTiming_LongestInputTimestamp3Name, 712);
PageLoad::kInteractiveTiming_LongestInputTimestamp4Name, 712);
}
}
......
......@@ -5569,6 +5569,25 @@ be describing additional metrics about the same event.
</summary>
</metric>
<metric name="InteractiveTiming.LongestInputDelay3">
<obsolete>
Removed on September 2019 in favor of InteractiveTiming.LongestInputDelay4
which includes events which otherwise would have been filtered.
</obsolete>
<summary>
Measures longest Input Delay, the longest duration between the hardware
timestamp and the start of event processing on the main thread for the
meaningful input per navigation. In ms.
</summary>
<aggregation>
<history>
<index fields="profile.country"/>
<statistics>
<quantiles type="std-percentiles"/>
</statistics>
</history>
</aggregation>
</metric>
<metric name="InteractiveTiming.LongestInputDelay4">
<summary>
Measures longest Input Delay, the longest duration between the hardware
timestamp and the start of event processing on the main thread for the
......@@ -5606,6 +5625,17 @@ be describing additional metrics about the same event.
</summary>
</metric>
<metric name="InteractiveTiming.LongestInputTimestamp3">
<obsolete>
Removed on February 2019 in favor of
InteractiveTiming.LongestInputTimestamp4 which includes inputs which would
have previously been filtered.
</obsolete>
<summary>
The duration between navigation start and the hardware timestamp of the
meaningful input with longest queuing delay per navigation. In ms.
</summary>
</metric>
<metric name="InteractiveTiming.LongestInputTimestamp4">
<summary>
The duration between navigation start and the hardware timestamp of the
meaningful input with longest queuing delay per navigation. In ms.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment