change delay to 2 seconds |
||
Issue descriptionChrome Version: 67.0.3396.0 OS: Android What steps will reproduce the problem? (1) navigate to page that has EoC suggestions (2) reverse scroll What is the expected result? if reverse scroll within 2 seconds, please show suggestions (for diary study) What happens instead? timer is 10 seconds Please use labels and text to provide additional information. If this is a regression (i.e., worked before), please consider using the bisect tool (https://www.chromium.org/developers/bisect-builds-py) to help us identify the root cause and more rapidly triage the issue. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Apr 19 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/1af760e13fb93d84c2105e318dfd4409db845be8 commit 1af760e13fb93d84c2105e318dfd4409db845be8 Author: Filip Gorski <fgorski@google.com> Date: Thu Apr 19 21:37:30 2018 [EoC] Change fetch triggring delay from 10 to 2 seconds Bug: 834914 Change-Id: I9909c1e6eb274a6e46963694fc8676e31aa66da7 Reviewed-on: https://chromium-review.googlesource.com/1020221 Reviewed-by: Patrick Noland <pnoland@chromium.org> Commit-Queue: Filip Gorski <fgorski@chromium.org> Cr-Commit-Position: refs/heads/master@{#552167} [modify] https://crrev.com/1af760e13fb93d84c2105e318dfd4409db845be8/chrome/android/java/src/org/chromium/chrome/browser/contextual_suggestions/FetchHelper.java
,
Apr 19 2018
|
||
►
Sign in to add a comment |
||
Comment 1 by twelling...@chromium.org
, Apr 19 2018