Scrolling in div doesn't function with opacity in a parent
Reported by
iiva...@sysm.eu,
Mar 14 2016
|
|||||||||
Issue description
Tested on "Android 4.2.1; 01v21_v89_jbl1a698_2g Build/JOP40D" phone and Windows 7 x64 desktop
scrolling doesn't work correctly on:
(Android) Chrome 49.0.2623.91
(Android) Chrome Dev 50.0.2661.26
and works correctly on:
(Windows 7) Google Chrome "Version 49.0.2623.87 m (64-bit)" (in "Galaxy S5" device mode)
(Android) Chrome 48.0.2564.95
(Android) Firefox 45.0
(Android) Opera 35.0.2070.100283
Example html:
<!DOCTYPE html>
<html>
<head>
<meta name="viewport" content="initial-scale=1.0">
<style>
html { font-size: 5em; }
body { opacity: .99;/*removing that, fixes the problem*/ }
div { overflow: auto; border: 1px solid; }
</style>
</head>
<body>
scrolling test<br><!--removing this line also fixes the problem-->
<div>
<span>0123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789</span>
</div>
</body>
</html>
Expected behavior: The div should be scrollable do to the width of the span
Observed behavior: The div shows scroll bar (briefly), but scrolling attempts aren't successful
Note: (In landscape) Removing the viewport meta tag and zooming out, creates area in the div where successful scrolling can be started, but the area doesn't cover the entire div (covers only the bottom 60-80 % of the div), and zooming in quickly reduces the height of the area to 0
Note: To test in Opera, the div's height must be limited
,
Mar 15 2016
I can reproduce this (for convenience: http://bokan.ca/bugs/594526.html). Using --disable-threaded-scrolling fixes the problem so this is an issue with the compositor scroll path. The fact that removing/adding opacity has an effect says to me that this is a problem with how we layerize the scrolling content. Unassigning and adding compositing label to get triage from someone who knows the area.
,
Mar 30 2016
+vollick@, could you please add the right labels/people?
,
Apr 6 2016
vollick@: friendly ping.
,
Apr 6 2016
,
Apr 13 2016
This bug seems to be caused by a hit test point and the layer it is checking to be incorrectly aligned. I have a fix in progress for this, will upload as soon as I can confirm the issue is what I thought.
,
Apr 14 2017
This issue has been available for more than 365 days, and should be re-evaluated. Please re-triage this issue. The Hotlist-Recharge-Cold label is applied for tracking purposes, and should not be removed after re-triaging the issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 17 2017
,
Apr 17 2017
,
Apr 18 2017
It is fixed (tested on (Android) Chrome 57.0.2987.132).
,
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
Per #10, closing this out. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by ppolise...@chromium.org
, Mar 14 2016Status: Assigned (was: Unconfirmed)