flackr@chromium.org Time between initiation of any input event and the renderer receiving and starting to process it. Team: input-dev@chromium.org. Warning: This metric may include reports from clients with low-resolution clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports will cause this metric to have an abnormal distribution. When considering revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the solution. mustaq@chromium.org nzolghadr@chromium.org Tracks the number of Android MotionEvents with ACTION_DOWN or ACTION_POINTER_DOWN or ACTION_BUTTON_PRESS for each ToolType (unknown, finger, mouse or stylus). Team: input-dev@chromium.org. liviutinta@chromium.org mustaq@chromium.org input-dev@chromium.org Records whether Browser User Activation Verification is successful or not. We are interested in how many times the Browser User Activation Verification fails vs how many times it succeeds. tbuckley@chromium.org The number of down events received per destination, input and form factor combination. Input is down events generated by mouse/touch/stylus. Form factor is down events generated by clamshell/touchviewLandscape/touchviewPortrait. Destination: Every down event that is targeted to each destination will be counted including those that don't have an effect. For example: Tapping on a disabled button inside the browser frame will be treated as down events on browser window. kuscher@google.com input-dev@chromium.org The gesture-events recognized and dispatched by the browser gesture recognizer. This replaces Ash.GestureCreated, which did not record events on Android and Windows. Note: this metric was expired from 2020-03-01 to 2023-04-04. flackr@chromium.org input-dev@chromium.org NOTE: this metric was expired from M97 to 2023-03-14. Overshoot distance in pixels between a predicted scroll position and the corresponding interpolated real scroll position that occurred at the frame time. The difference between {ScoreType} and Frame{ScoreType} is the former uses prediction time and the later uses frame time. Team: input-dev@chromium.org. flackr@chromium.org input-dev@chromium.org NOTE: this metric was expired from M97 to 2023-03-14. Euclidean distance in pixels between two successive variations of touch scroll deltas which are the difference between a predicted scroll position and its corresponding interpolated real position that occurred at prediction time. Team: input-dev@chromium.org. flackr@chromium.org input-dev@chromium.org NOTE: this metric was expired from M97 to 2023-03-14. Euclidean distance in pixels between two successive variations of touch scroll deltas which are the difference between a predicted scroll position and the interpolated real position that occurred at frame time. Team: input-dev@chromium.org. flackr@chromium.org input-dev@chromium.org NOTE: this metric was expired from M97 to 2023-03-14. Overshoot distance in pixels between a predicted scroll position and the corresponding interpolated real scroll position that occurred at the frame time. Team: input-dev@chromium.org. kartarsingh@google.com mekk@google.com woa-performance-team@google.com NOTE: The metric is deprecated and renamed to Event.ScrollJank.DelayedFramesPercentage.FixedWindow A frame is deemed janky during a scroll if there was no presented frame in the previous vsync, and the current frame contains input that was not presented during the missed frame. Missed input is determined by comparing the timestamp of the earliest input of the current frame, to that of the last input of the previously presented frame. If the delta of the timestamps is less than a vsync + vsync/2, then the input is considered to have been intended for the missed frame. This metric reports the percentage of delayed frames within an arbitrary window of 64 frames. For more details about this metric, please check http://doc/1Y0u0Tq5eUZff75nYUzQVw6JxmbZAW9m64pJidmnGWsY kartarsingh@google.com mekk@google.com woa-performance-team@google.com NOTE: The metric is deprecated and renamed to Event.ScrollJank.MissedVsyncsSum.FixedWindow A frame is deemed janky during a scroll if there was no presented frame in the previous vsync, and the current frame contains input that was not presented during the missed frame. Missed input is determined by comparing the timestamp of the earliest input of the current frame, to that of the last input of the previously presented frame. If the delta of the timestamps is less than a vsync + vsync/2, then the input is considered to have been intended for the missed frame. For janky frames, this metric counts number of vsyncs the frame was delayed by. The metric gets reported for a windows of 64 reported frames. For more details about this metric, please check http://doc/1Y0u0Tq5eUZff75nYUzQVw6JxmbZAW9m64pJidmnGWsY mekk@google.com woa-performance@google.com A frame is deemed janky if an irregular jump in screen displacement occured in consecutive frames, this metric is the percentage of those janky frames per 50 produced frames and is only emitted if a scroll has more than 50 frames in sa sequence. This metric is used to asses the scrolling prediction performance as the scroll predictor should smooth out those irregular jumps. For more details about this metric, please check http://doc/1Y0u0Tq5eUZff75nYUzQVw6JxmbZAW9m64pJidmnGWsY. nuskos@google.com woa-performance@google.com IMPORTANT: This was deprecated and stopped being emitted due to overflow from the counters being emitted in Microseconds instead of milliseconds like it was supposed to. Please see Event.Jank.ScrollUpdate.TotalJankyAndNonJankyDuration2. Each time a ScrollUpdate event which was displayed on the screen is processed, an amount of samples equal to the event processing duration in milliseconds is emitted into the corresponding bucket. Thus the ratio of the two represents the average amount of time scrolling is janky. nuskos@google.com woa-performance@google.com Each time a ScrollUpdate event which was displayed on the screen is processed, an amount of samples equal to the event processing duration in milliseconds is emitted into the corresponding bucket. Thus the ratio of the two represents the average amount of time scrolling is janky. mekk@google.com woa-performance@google.com This metric is the ratio between a larger screen displacement divided by a following small screen displacement {ScrollSpeed}. If the larger screen displacement was deemed janky given the predictor performance, and is only emitted if there is {VsyncStatus}. This metric is used to asses the scrolling prediction performance as the scroll predictor should smooth out those irregular jumps. For more details about this metric, please check http://doc/1Y0u0Tq5eUZff75nYUzQVw6JxmbZAW9m64pJidmnGWsY. flackr@chromium.org input-dev@chromium.org NOTE: This metric is deprecated in favor of EventLatency.KeyPressed.TotalLatency metric (see crbug.com/1054021). Time between the OS receiving a keyboard event and the resulting GPU frame swap. If no swap was induced by the event, no recording is made. Only recorded for key presses. Warning: This metric may include reports from clients with low-resolution clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports will cause this metric to have an abnormal distribution. When considering revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the solution. nzolghadr@chromium.org input-dev@chromium.org NOTE: This metric is deprecated in favor of EventLatency.GesturePinch*.TotalLatency metrics (see crbug.com/1054021). Time between the OS receiving a touchpad pinch event and the resulting GPU frame swap. If no swap was induced by the event, no recording is made. pdr@chromium.org paint-dev@chromium.org Duration of a non-resurive hitTest operation. The hit test is non-recursive when the AllowChildFrameContent flag is clear. See also Event.Latency.HitTestRecusrive. Team: paint-dev@chromium.org. Warning: This metric may include reports from clients with low-resolution clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports will cause this metric to have an abnormal distribution. When considering revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the solution. pdr@chromium.org paint-dev@chromium.org Duration of a recursive hitTest operation. The hit test is recursive when the AllowChildFrameContent flag is set. See also Event.Latency.HitTest. Team: paint-dev@chromium.org. Warning: This metric may include reports from clients with low-resolution clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports will cause this metric to have an abnormal distribution. When considering revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the solution. flackr@chromium.org joenotcharles@google.com input-dev@chromium.org Time between input event received by OS and sent to Chrome, recorded for each event when it is received by Chrome. Replaced Event.Latency.OS which was calculated incorrectly on Windows. Warning: On Windows, the timestamps of most events come from a clock with a several msec resolution so will have an abnormal distribution even when TimeTicks::IsHighResolution returns true. The exception is touch events which usually come from the high-resolution clock when TimeTicks::IsHighResolution returns true. nzolghadr@chromium.org gerchiko@microsoft.com input-dev@chromium.org speed-metrics-dev@chromium.org NOTE: This metric is deprecated in favor of EventLatency.FirstGestureScrollUpdate.Scrollbar.TotalLatency metric (see crbug.com/1054021). Time between initial creation of an input event that resulted in a scrollbar scroll and the start of the frame swap on the GPU service caused by the generated ScrollUpdate gesture event if that ScrollUpdate is the first such event in a given scroll gesture event sequence. If no swap was induced by the event, no recording is made. Do not modify this metric in any way without contacting speed-metrics-dev@chromium.org. Warning: This metric may include reports from clients with low-resolution clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports will cause this metric to have an abnormal distribution. When considering revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the solution. nzolghadr@chromium.org NOTE: This metric is deprecated in favor of EventLatency.FirstGestureScrollUpdate.TotalLatency metric (see crbug.com/1054021). Time between initial creation of a wheel/touch event and start of the frame swap on the GPU service caused by the generated ScrollUpdate gesture event if that ScrollUpdate is the first such event in a given scroll gesture event sequence. If no swap was induced by the event, no recording is made. If no swap was induced by the event, no recording is made. Team: input-dev@chromium.org. flackr@chromium.org sahir.vellani@microsoft.com input-dev@chromium.org Measures an average distance that represents how the page sticks to the finger when user scrolls. Only reports touch scrolling. See https://docs.google.com/document/d/154jddNiKtxELBvrjLz9v6A7sA1J3iwQQzySHgtY12Oo/ This is the lag observed in processing the Gesture Scroll Begin Event. In each touch interaction there is a GSB followed by multiple Gesture Scroll Updates, which are separately logged by Event.Latency.ScrollUpdate.Touch.AverageLagPresentation. Note: This histogram was expired from 2022-05-01 to 2023-06-20. Team: input-dev@chromium.org. flackr@chromium.org sahir.vellani@microsoft.com input-dev@chromium.org Measures an average distance that represents how the page sticks to the finger when user scrolls if prediction was disabled. Only reports touch scrolling. See https://docs.google.com/document/d/154jddNiKtxELBvrjLz9v6A7sA1J3iwQQzySHgtY12Oo/ This is the lag observed in processing the Gesture Scroll Begin Event. In each touch interaction there is a GSB followed by multiple Gesture Scroll Updates, which are separately logged by Event.Latency.ScrollUpdate.Touch.AverageLagPresentation. Note: This histogram was expired from 2022-11-23 to 2023-06-20. Team: input-dev@chromium.org. flackr@chromium.org input-dev@chromium.org speed-metrics-dev@chromium.org NOTE: This metric is deprecated in favor of EventLatency.FirstGestureScrollUpdate.Touchscreen.TotalLatency metric (see crbug.com/1054021). Time between initial creation of a touch event and the start of the frame swap on the GPU service caused by the generated ScrollUpdate gesture event if that ScrollUpdate is the first such event in a given scroll gesture event sequence. If no swap was induced by the event, no recording is made. Do not modify this metric in any way without contacting speed-metrics-dev@chromium.org. Warning: This metric may include reports from clients with low-resolution clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports will cause this metric to have an abnormal distribution. When considering revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the solution. {TopControlsState} flackr@chromium.org NOTE: This metric is deprecated in favor of EventLatency.FirstGestureScrollUpdate.Wheel.TotalLatency metric (see crbug.com/1054021). Time between initial creation of a wheel event and the start of the frame swap on the GPU service caused by the generated ScrollUpdate gesture event if that ScrollUpdate is the first such event in a given scroll gesture event sequence. If no swap was induced by the event, no recording is made. Team: input-dev@chromium.org. Warning: This metric may include reports from clients with low-resolution clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports will cause this metric to have an abnormal distribution. When considering revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the solution. Removed in 2022-09. Replaced by EventLatency.InertialGestureScrollUpdate.Touchscreen.TotalLatency. flackr@chromium.org input-dev@chromium.org Time between initial creation of a ScrollUpdate gesture event generated from a touchscreen fling and the start of the frame swap on the GPU service caused by the generated ScrollUpdate gesture event. If no swap was induced by the event, no recording is made. Team: input-dev@chromium.org. Warning: This metric may include reports from clients with low-resolution clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports will cause this metric to have an abnormal distribution. When considering revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the solution. ddrone@google.com chrometto-team@google.com Tracks janky frames while processing scroll events, which are defined as frames taking longer than half of vsync interval compared to previous or next frame. ddrone@google.com chrometto-team@google.com Total duration (wall time in milliseconds of potentially concurrent events) of LatencyInfo::GestureScrollUpdate events that are detected as janky during a particular scroll. ddrone@google.com chrometto-team@google.com Percentage of duration of scroll events that are detected as janky during a particular scroll. ddrone@google.com chrometto-team@google.com Count of LatencyInfo::GestureScrollUpdate events that are detected as janky during a particular scroll. flackr@chromium.org arakeri@microsoft.com input-dev@chromium.org speed-metrics-dev@chromium.org NOTE: This metric is deprecated in favor of EventLatency.GestureScrollUpdate.Scrollbar.TotalLatency metric (see crbug.com/1054021). Time between initial creation of a scrollbar event and start of the frame swap on the GPU service caused by the generated ScrollUpdate gesture event. If no swap was induced by the event, no recording is made. The first GSU of every scrolling sequence is excluded from this metric. Do not modify this metric in any way without contacting speed-metrics-dev@chromium.org. Warning: This metric may include reports from clients with low-resolution clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports will cause this metric to have an abnormal distribution. When considering revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the solution. nzolghadr@chromium.org NOTE: This metric is deprecated in favor of EventLatency.GestureScrollUpdate.TotalLatency metric (see crbug.com/1054021). Time between initial creation of a wheel/touch event and start of the frame swap on the GPU service caused by the generated ScrollUpdate gesture event. If no swap was induced by the event, no recording is made. The first GSU of every scrolling sequence is excluded from this metric. Team: input-dev@chromium.org. ddrone@google.com chrometto-team@google.com Total duration (wall time in milliseconds of potentially concurrent events) of LatencyInfo::GestureScrollUpdate events during a particular scroll. ddrone@google.com chrometto-team@google.com Count of LatencyInfo::GestureScrollUpdate events during a particular scroll. flackr@chromium.org sahir.vellani@microsoft.com input-dev@chromium.org Measures an average distance that represents how the page sticks to the finger when user scrolls. Only reports touch scrolling. See https://docs.google.com/document/d/154jddNiKtxELBvrjLz9v6A7sA1J3iwQQzySHgtY12Oo/ This is the lag observed in processing the Gesture Scroll Updates occurring in the lifetime of a scroll interaction. Note: This histogram was expired from 2022-12-25 to 2023-06-20. Team: input-dev@chromium.org. flackr@chromium.org sahir.vellani@microsoft.com input-dev@chromium.org Measures an average distance that represents how the page sticks to the finger when user scrolls if prediction was disabled. Only reports touch scrolling. See https://docs.google.com/document/d/154jddNiKtxELBvrjLz9v6A7sA1J3iwQQzySHgtY12Oo/ This is the lag observed in processing the Gesture Scroll Updates occurring in the lifetime of a scroll interaction. Note: This histogram was expired from 2022-11-23 to 2023-06-12. Team: input-dev@chromium.org. flackr@chromium.org sahir.vellani@microsoft.com input-dev@chromium.org Percentage of touch lag that prediction wasn't able to remove. This is the ratio (Lag_with_prediction)/(Lag_without_prediction). Lag is the average distance between the finger and page positons during touch scrolling. 0% means all the lag existing before prediction was removed. 100% means that prediction had no impact. Greater than 100% means that prediction introduced more lag. This metric doesn't distinguish between OverPrediction and UnderPrediction. A same absolute value of OverPrediction or UnderPrediction will result in the same RemainingLagPercentage value. Lag_with_prediction = Event.Latency.ScrollUpdate.Touch.AverageLagPresentation Lag_without_prediction = Event.Latency.ScrollUpdate.Touch.AverageLagPresentation.NoPrediction Note: This histogram was expired from 2022-11-23 to 2023-06-20. Team: input-dev@chromium.org. flackr@chromium.org sahir.vellani@microsoft.com input-dev@chromium.org Improvement of prediction in touch lag. It is defined as (Lag_without_prediction - Lag_with_prediction). Lag is the distance between the finger position and the rendered position. When positive, prediction improves touch performance (reduces lag). When negative, prediction worsens touch performance (increases lag). The duration of the interaction/interval is either 1s, or the time from when the user starts scrolling to lifting the finger, whichever is smaller. This metric uses directionless distances, therefore it doesn't distinguish between OverPrediction and UnderPrediction. A same absolute value of OverPrediction or UnderPrediction will result in the same PredictionImpact value. Lag_with_prediction = Event.Latency.ScrollUpdate.Touch.AverageLagPresentation Lag_without_prediction = Event.Latency.ScrollUpdate.Touch.AverageLagPresentation.NoPrediction Note: This histogram was expired from 2022-11-23 to 2023-06-20. Team: input-dev@chromium.org. flackr@chromium.org sullivan@chromium.org input-dev@chromium.org speed-metrics-dev@chromium.org chrome-analysis-team@google.com NOTE: This metric is deprecated in favor of EventLatency.GestureScrollUpdate.Touchscreen.TotalLatency metric (see crbug.com/1054021). Time between initial creation of a touch event and start of the frame swap on the GPU service caused by the generated ScrollUpdate gesture event. If no swap was induced by the event, no recording is made. The first GSU of every scrolling sequence is excluded from this metric. Do not modify this metric in any way without contacting speed-metrics-dev@chromium.org AND chrome-analysis-team@google.com. Warning: This metric may include reports from clients with low-resolution clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports will cause this metric to have an abnormal distribution. When considering revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the solution. {TopControlsState} flackr@chromium.org NOTE: This metric is deprecated in favor of EventLatency.GestureScrollUpdate.Wheel.TotalLatency metric (see crbug.com/1054021). Time between initial creation of a wheel event and start of the frame swap on the GPU service caused by the generated ScrollUpdate gesture event. If no swap was induced by the event, no recording is made. The first GSU of every scrolling sequence is excluded from this metric. Team: input-dev@chromium.org. Warning: This metric may include reports from clients with low-resolution clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports will cause this metric to have an abnormal distribution. When considering revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the solution. mustaq@chromium.org input-dev@chromium.org The maximum Euclidean distance (in DIPs, device independent pixels) a single-pointer gesture travels from its starting position during the period the gesture has been active. The histogram is measured separately for every pointer type that can be used in gesture recognition: finger, and pen in drawing/eraser mode. The type names used here follow the corresponding labels in |MotionEvent.ToolType|. hajimehoshi@chromium.org fergal@chromium.org Records whether the pageshow event had its persisted flag set in renderer or browser. This flag is on if and only if the page is restored from back-forward cache. This flag is off e.g. during the page load. This is recorded when pageshow event fires on a main frame in renderer, or when browser triggers this event on a main frame. This was a boolean on M95 and before, is extended to an enum EventPageShoerPersisted as of M96. hajimehoshi@chromium.org fergal@chromium.org When we send a PageLifecycleState update that should trigger a pageshow event with its persisted flag set and then the renderer exits, this records the status of the process. This is an enum (base::TerminationStatus in base/process/kill.h) but the values vary by platform so we cannot use a regular enum metric. This is temporary debugging for https://crbug.com/1234634. hajimehoshi@chromium.org fergal@chromium.org When we send a PageLifecycleState update that should trigger a pageshow event with its persisted flag set and have not yet received an ack, we log how long it takes for certain events to occur. This is temporary debugging for https://crbug.com/1234634. dtapuska@chromium.org The result of handling of MouseWheel, TouchStart, TouchMove, TouchEnd events in the renderer. Team: input-dev@chromium.org. kartarsingh@google.com mekk@google.com woa-performance-team@google.com A frame is deemed janky during a scroll if there was no presented frame in the previous vsync, and the current frame contains input that was not presented during the missed frame. Missed input is determined by comparing the timestamp of the earliest input of the current frame, to that of the last input of the previously presented frame. If the delta of the timestamps is less than a vsync + vsync/2, then the input is considered to have been intended for the missed frame. This metric reports the percentage of delayed frames within a window of size 64. For more details about this metric, please check http://doc/1Y0u0Tq5eUZff75nYUzQVw6JxmbZAW9m64pJidmnGWsY kartarsingh@google.com mekk@google.com woa-performance-team@google.com A frame is deemed janky during a scroll if there was no presented frame in the previous vsync, and the current frame contains input that was not presented during the missed frame. Missed input is determined by comparing the timestamp of the earliest input of the current frame, to that of the last input of the previously presented frame. If the delta of the timestamps is less than a vsync + vsync/2, then the input is considered to have been intended for the missed frame. This metric reports the percentage of delayed frames within a scroll. This metric gets reported for {Length}. For more details about this metric, please check http://doc/1Y0u0Tq5eUZff75nYUzQVw6JxmbZAW9m64pJidmnGWsY kartarsingh@google.com mekk@google.com woa-performance-team@google.com A frame is deemed janky during a scroll if there was no presented frame in the previous vsync, and the current frame contains input that was not presented during the missed frame. Missed input is determined by comparing the timestamp of the earliest input of the current frame, to that of the last input of the previously presented frame. If the delta of the timestamps is less than a vsync + vsync/2, then the input is considered to have been intended for the missed frame. This metric counts number of vsyncs the frame was delayed by(which could be zero). The metric gets reported for every frame. Please see Event.ScrollJank.MissedVsyncs* for other related histograms aggregated over a fixed window and emitted once per window. For more details about this metric, please check http://doc/1Y0u0Tq5eUZff75nYUzQVw6JxmbZAW9m64pJidmnGWsY kartarsingh@google.com mekk@google.com woa-performance-team@google.com A frame is deemed janky during a scroll if there was no presented frame in the previous vsync, and the current frame contains input that was not presented during the missed frame. Missed input is determined by comparing the timestamp of the earliest input of the current frame, to that of the last input of the previously presented frame. If the delta of the timestamps is less than a vsync + vsync/2, then the input is considered to have been intended for the missed frame. This metric reports the {Operator} in window of size 64. Metric emits zeros as well i.e. the case when no frames were delayed. Please see Event.ScrollJank.MissedVsyncs.PerFrame for unaggregated version of this histogram. For more details about this metric, please check http://doc/1Y0u0Tq5eUZff75nYUzQVw6JxmbZAW9m64pJidmnGWsY kartarsingh@google.com mekk@google.com woa-performance-team@google.com A frame is deemed janky during a scroll if there was no presented frame in the previous vsync, and the current frame contains input that was not presented during the missed frame. Missed input is determined by comparing the timestamp of the earliest input of the current frame, to that of the last input of the previously presented frame. If the delta of the timestamps is less than a vsync + vsync/2, then the input is considered to have been intended for the missed frame. This metric reports the {Operator} in scroll. Metric emits zeros as well i.e. the case when no frames were delayed. The metric gets reported for {Length}. Please see Event.ScrollJank.MissedVsyncs.PerFrame for unaggregated version of this histogram. For more details about this metric, please check http://doc/1Y0u0Tq5eUZff75nYUzQVw6JxmbZAW9m64pJidmnGWsY flackr@chromium.org input-dev@chromium.org On non-mobile sites, gesture taps are delayed to prevent double taps from sending a click event. This stat counts the number of taps that are delayed by the double-tap delay versus those that are sent immediately on mobile sites. Team: input-dev@chromium.org. charliea@chromium.org nzolghadr@chromium.org Whether a given touch event is filtered by the passthrough touch event queue or not. If the event was filtered, a reason is given. Potential reasons for filtering include the page not having any registered touch handlers and the renderer process not responding to previous touch events. Team: input-dev@chromium.org kuscher@google.com rbyers@chromium.org The gesture-events recognized and dispatched for UI components owned by the browser. This histogram was created as part of separating gesture events between the browser and Ash (crbug.com/826476). The enums are extracted from Ash.GestureTarget. flackr@chromium.org input-dev@chromium.org On non-mobile-optimized (desktop) sites, whether the ack response from the renderer for any event in a contiguous touch sequence exceeds the desktop-specific timeout threshold. Warning: This histogram has incomplete data. It expired on 2021-08-15 and then got re-enabled on M110. Team: input-dev@chromium.org. flackr@chromium.org input-dev@chromium.org On mobile-optimized sites, whether the ack response from the renderer for any event in a contiguous touch sequence exceeds the mobile-specific timeout threshold. Warning: This histogram has incomplete data. It expired on 2021-08-15 and then got re-enabled on M110. Team: input-dev@chromium.org. nzolghadr@chromium.org Duration of touch selection sequence which finished with the user selecting one of the text manipulation actions, such as copy, cut, or paste. The duration is measured from the moment the text selection handles are shown, and until the action is executed. nzolghadr@chromium.org Whether the touch selection sequence ended with the user selecting one of the text manipulation actions, such as copy, cut, or paste. after startup). Sequences ending with such action are considered successful. nzolghadr@chromium.org Duration of touch selection sequence which involved dragging a text selection handle. The duration is measured from the moment the text selection handles are shown, and until they are dismissed. mustaq@chromium.org input-dev@chromium.org Tracks the notification-type for the user activation that resulted in a successful call for an activation-gated API (of type sticky, transient or consuming). rjkroege@chromium.org adunaev@igalia.com Delay between the drag coming into the window and the window is actually notified. jonross@chromium.org graphics-dev@chromium.org chrome-analysis-team@google.com When a user performs a scroll using touchscreen, a sequence of touch-move events are generated leading to a sequence of gesture-scroll-update events. This metric measures total latency of those gesture-scroll-update events excluding the first one in the sequence and those that are inertial (i.e. generated as a result of a user fling). Total latency means the time from when the touch-move causing a gesture-scroll-update is generated until when the changes caused by the event are successfully presented on the screen. This histogram will eventually be replaced by its TotalLatency2 equivalent which uses an improved bucketing. This histogram only records metrics on machines with high-resolution clocks. jonross@chromium.org graphics-dev@chromium.org When a user performs a scroll using touchscreen, a sequence of touch-move events are generated leading to a sequence of gesture-scroll-update events. This metric measures total latency of those gesture-scroll-update events excluding the first one in the sequence and those that are inertial (i.e. generated as a result of a user fling). Total latency means the time from when the touch-move causing a gesture-scroll-update is generated until when the changes caused by the event are successfully presented on the screen. This histogram is similar to its TotalLatency (non-v2) equivalent except that it uses an improved bucketing. We will eventually remove the non-v2 version. This histogram only records metrics on machines with high-resolution clocks. jonross@chromium.org graphics-dev@chromium.org Tracks total latency of {NonTouchscreenScrollInputType} gesture-scroll-update events that are non-inertial (i.e. not generated due to a user fling) and not the first one in a scroll sequence, from when the user input causing the event is performed until the frame caused by the event is submitted by the GPU service and presented successfully on the screen. {Version}. This histogram only records metrics on machines with high-resolution clocks. jonross@chromium.org graphics-dev@chromium.org Tracks total latency of all event types, from when the user input causing the event is performed until the frame caused by the event is submitted by the GPU service and presented successfully on the screen. This histogram only records metrics on machines with high-resolution clocks. jonross@chromium.org graphics-dev@chromium.org Tracks total latency of {ScrollInputType} {NonGsuScrollEventType}, from when the user input causing the event is performed until the frame caused by the event is submitted by the GPU service and presented successfully on the screen. {Version}. This histogram only records metrics on machines with high-resolution clocks. jonross@chromium.org graphics-dev@chromium.org Tracks total latency of {NonScrollPinchEventType}, from when the user input causing the event is performed generated until the frame caused by the event is submitted by the GPU service and presented successfully on the screen. This histogram only records metrics on machines with high-resolution clocks. jonross@chromium.org graphics-dev@chromium.org Tracks total latency of {PinchInputType} {PinchEventType}, from when the user input causing the event is performed until the frame caused by the event is submitted by the GPU service and presented successfully on the screen. This histogram only records metrics on machines with high-resolution clocks. jonross@chromium.org graphics-dev@chromium.org Tracks total latency of {ScrollEventType}, from when the user input causing the event is performed generated until the frame caused by the event is submitted by the GPU service and presented successfully on the screen. {Version}. This histogram only records metrics on machines with high-resolution clocks.