Issue metadata
Sign in to add a comment
|
Chrome browser: 1st click event is not captured after scrolling |
||||||||||||||||||||||
Issue descriptionGoogle Chrome 67.0.3381.0 (Official Build) dev (64-bit) Revision 0 Platform 10525.0.0 (Official Build) dev-channel eve What steps will reproduce the problem? 1. Open Chrome browser and enter any text to search 2. After search results are displayed, scroll down the page and click on any search result. Click event is not captured 3. Click on the search result again. Observe that click is captured 4. Open new tab and search with any text. Scroll down and click on any result. Click event is not captured. 5. Scroll up and click on search result. Click event is not captured. What is the expected result? Click events should be captured properly What happens instead? First click event is not captured after scrolling.
,
Apr 5 2018
How frequently does this occur?
,
Apr 5 2018
,
Apr 12 2018
Do you scroll with wheel/trackpad or touchscreen? Do you stop for the scroll to finish and then try to click or click while the scroll is in inertial state (fling)? If you scroll and while the page is still scrolling do a mouse press, the mouse press will cancel the fling and then when you do mouse release it won't trigger a click. This is an intended behavior to make sure that the click that cancels fling gets suppressed. Comment 0 doesn't explain if this used to work or not? Do you think this is a recent regression?
,
Apr 12 2018
Do you scroll with wheel/trackpad or touchscreen? I scrolled with 2 finger scroll on touchpad Do you stop for the scroll to finish and then try to click or click while the scroll is in inertial state (fling)? I clicked immediately after the scroll was complete. Comment 0 doesn't explain if this used to work or not? Do you think this is a recent regression? Unfortunately, I was unable to repro the scenario after c#1.
,
Apr 13 2018
Have you been able to repro since? Does it go away immediately after it happens? If not, a trace would be very helpful: https://www.chromium.org/developers/how-tos/submitting-a-performance-bug Unfortunately, without a repro or some tracing data this isn't very actionable. I'll leave the bug open for a while in case we can get more data that might be helpful.
,
Apr 19 2018
I'm not able to repro the issue either. Reported if you happen to get a trace and maybe a screen cast feel free to comment here or open a new bug for that.
,
Apr 27 2018
The NextAction date has arrived: 2018-04-27
,
Apr 27 2018
Marking WontFix as the issue is not reproducible. Will log a new bug with feedback report and trace if I see this issue again. Thanks!! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by sdantul...@chromium.org
, Mar 30 2018