Issue metadata
Sign in to add a comment
|
Bug on Chrome: hidden overflowing region still triggers mouse events.
Reported by
hback...@gmail.com,
Dec 5 2016
|
||||||||||||||||||||||
Issue descriptionChrome Version : 54.0.2840.99 (Official Build) m (32-bit) URLs (if applicable) : http://stackoverflow.com/questions/40964326/prevent-overflowing-elements-hidden-region-from-being-clickable Other browsers tested: Firefox: OK IE: OK What steps will reproduce the problem? (1) Define a div and set the css attribute overflow to hidden. (2) Define a new div inside the one defined in (1) so that it overflows the parent container; (3) Customize the :hover selector for div created in (2) so that it changes color on mouse hover. (4) Hover the mouse outside of the first div but near the second div and you will notice the second div changing color. What is the expected result? The second div should have changed its color because the user did not hover the mouse over the visible region. What happens instead? As the user did not hover the mouse over the visible region for second div it should have changed color. I believe this is happening, because the browser is also taking into account the invisible region os the second div, the part that overflows the first div. See this link for an example of the said behaviour: http://stackoverflow.com/questions/40964326/prevent-overflowing-elements-hidden-region-from-being-clickable
,
Dec 5 2016
It seems I cannot edit my bug report and I mixed it up regarding the expected and the actual result. Therefore, take into account these descriptions instead: What is the expected result? The second div should have not changed its color because the user did not hover the mouse over the visible region. What happens instead? The second div changed its color.
,
Dec 6 2016
,
Dec 6 2016
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by dtapu...@chromium.org
, Dec 5 2016