Add Flag to Prevent Timed Locking of Android Controls
BrowserStateBrowserControlsVisibilityDelegate has a timer which is used to ensure that the browser controls are visible for a minimum amount of time. However this causes a race condition for telemetry tests. The controls can become unlocked after telemetry has triggered a scroll. This leads to incidental compositor frame submissions which affect the performance. Pinpoint job with associated traces for the jank: https://pinpoint-dot-chromeperf.appspot.com/job/11a923eae40000 This change adds an Android specific flag to prevent locking the controls for this timed duration. Page loading will still cause locks. Though tests tend to wait for loading to complete already, so that lock will not affect the measurements TEST=Ran telemetry rendering.mobile scrolling stories Bug: 896264 Change-Id: Ia1b3451cf4e4b7170b3478861a4e91316ab3bee5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1696189Reviewed-by:Yaron Friedman <yfriedman@chromium.org> Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Commit-Queue: Jonathan Ross <jonross@chromium.org> Cr-Commit-Position: refs/heads/master@{#676950}
Showing
Please register or sign in to comment