Issue metadata
Sign in to add a comment
|
Scroll blocked after transform scale
Reported by
dd6...@gmail.com,
May 3 2018
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36 Steps to reproduce the problem: 1. Mouse on some element with image with :hover transform: scale(1.1, 1.1) (1.1 for example); 2. Then try to scroll page without mouse moving (not a pixel at all) 3. Scroll doesn't work. After user moves mouse scroll start working. What is the expected behavior? What went wrong? It is strange issue and works in 30% of cases. As I've said before, if user constantly moving the mouse - all works fine. But if you using only scrollweel, then cursor hovering on image, it scaling, and after user can't scroll page. https://jsfiddle.net/dd64ru/f6p20Lu9/ It more visible if you have gallery with much images and it's awful Did this work before? N/A Does this work in other browsers? Yes Chrome version: 65.0.3325.181 Channel: stable OS Version: 10.0 Flash Version:
,
May 4 2018
,
May 10 2018
Can not reproduce at 66.0.3359.139 and 68.0.3426.0. Please try out the latest canary to see if you can still reproduce.
,
May 11 2018
Unable to reproduce the issue on chrome reported version 65.0.3325.181 using windows 10 with steps mentioned below: 1) Launched chrome reported version and navigated to URL: https://jsfiddle.net/dd64ru/f6p20Lu9/ 2) By using mouse scroll wheel, scrolled the page without moving the mouse, able to scroll the page without any issues @Reporter: Please find the attached screencast for your reference and let us know if we missed anything in reproducing the issue, try to test this issue by creating new person with no apps and extensions in it or test this issue on latest chrome stable. You can download chrome latest stable from URL: https://www.chromium.org/getting-involved/dev-channel. Thanks!
,
May 17 2018
dd64ru@, could you please try to reproduce the issue in Chrome Canary and let us know if it still exists there. If so, please capture and attach a trace to this bug following instructions here: https://www.chromium.org/developers/how-tos/submitting-a-performance-bug Unfortunately we can't reproduce locally - without some additional information this isn't very actionable and we'll have to close the bug.
,
May 24 2018
The NextAction date has arrived: 2018-05-24
,
May 31 2018
Closing due to lack of additional information. Feel free to reply and we can reopen. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by e...@chromium.org
, May 3 2018