mouseover target is incorrect on border of scrolled element
Reported by
m...@hansmeyer.com,
Apr 3 2017
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.110 Safari/537.36 Steps to reproduce the problem: See attachment. mouseover top border (orange area) of #scrolled-area element while a contained .item-inner element is scrolled underneath it. What is the expected behavior? mouseover target should be #scrolled-area element, or at least the .item-inner element underneath cursor. What went wrong? mouseover target is .item element. Did this work before? N/A Does this work in other browsers? Yes Chrome version: 57.0.2987.110 Channel: stable OS Version: 10.0 Flash Version:
,
Apr 4 2017
,
Apr 4 2017
durga.behara@, does this reproduce on Mac? Scrollbars are drawn differently on Mac, so it is plausible that that problems only occurs there. Also, reporter, what are your Mac OS scrollbar preferences set to?
,
Apr 15 2017
Thank you for providing more feedback. Adding requester "durga.behera@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 15 2017
Also reproduced on: - Chrome Version 59.0.3071.0 (Official Build) canary (64-bit) - macOS Sierra Chrome Version 57.0.2987.133 (64-bit) - (default macOS scrollbar prefs)
,
Apr 17 2017
I cannot reproduce on Win 10 Canary Version 60.0.3073.0 (Official Build) canary (64-bit), nor on Win 10 Version 58.0.3029.54 beta (64-bit). I can reproduce on Mac 60.0.3073.0 with scrollbar setting "Always". It's clear that the border is not catching the hit event, or that the clip for the scrolling contents is being ignored while clipping (probably the latter).
,
Apr 17 2017
Reproduces on windows, and probably Linux, with preferCompositingToLCDText.
,
Apr 17 2017
Let me know if there's anything I could tweak on my end (chrome flag?) to help isolate.
,
Apr 18 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 18 2018
Still wrong. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by nyerramilli@chromium.org
, Apr 3 2017