Elements fail to appear on scroll in nested scroll container with border-radius
Reported by
tburn...@hubspot.com,
Dec 21 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36 Steps to reproduce the problem: 1. Go to https://codepen.io/TrevorBurnham/pen/XVjpJG/ 2. Scroll down to see more list items. What is the expected behavior? The list items that were not visible initially should become visible as they scroll into view. What went wrong? The list items that were not visible initially remain invisible until horizontal scrolling is triggered. Notice that the issue goes away if the "border-radius: 1px" rule is removed from the inner scroll container. It also goes away if you set "backface-visibility: hidden" or "transform: translateZ(0)" on the list items. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 63.0.3239.84 Channel: n/a OS Version: OS X 10.12.6 Flash Version: Shockwave Flash 28.0 r0 In my app, the reason I'm adding border-radius to a nested scrollable container is as a workaround for another Chromium bug involving "background-attachment": https://www.quirksmode.org/blog/archives/2016/07/the_backgrounda.html
,
Dec 27 2017
tburnham@ thanks for the issue. Able to reproduce this issue on the latest Stable 63.0.3239.108 and Canary 65.0.3305.0 on Windows 10, Ubuntu 14.04 and Mac OS 10.12.6 following the steps mentioned in the original comment. This issue is seen from M50 chrome builds. Hence this issue as Non-Regression. Marking as Untriaged for further updates from Dev. Thanks!
,
Jan 4 2018
Repro'd on Mac but not on Linux. Turning on paint-flashing shows that the list items show up when we paint and we don't until horizontal scrolling so I think this is an invalidation issue.
,
Jan 16 2018
,
Jan 16
(6 days ago)
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
,
Yesterday
(44 hours ago)
Appears to have been fixed. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by krajshree@chromium.org
, Dec 26 2017