Element unrenders on scroll, shows only background color
Reported by
gdaolewe...@gmail.com,
Mar 23 2016
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36 Example URL: Steps to reproduce the problem: See attached screenshots: 1. User loads email thread with particular content in IBM Verse (have not yet narrowed down what is particular about the content that causes this, and it still occurs with all text replaced with the 'a' character) (see chrome_noscroll_noissue.png) 2. Scroll a short distance into this thread 3. Observe content disappear, showing only gray background color (see chrome_scroll_issue.png) 4. Scroll back up to the top, content renders properly again We have reproduced this in our app (IBM Verse) only when showing particular mail content in a particular user's account. I haven't been able to create a minimum reproducible case, so I'm working on trimming out any user data and as much markup outside the affected area as possible to create an example and will upload that when I have approval. I'm hoping that having screenshots and the bisect range will be helpful otherwise. What is the expected behavior? The content should be rendered as it was before scrolling. This works correctly in Safari, Firefox, and Chromium revisions prior to/including 361270 (see firefox_scroll_no_issue.png). What went wrong? The content is replaced with the background color. Controls inside the content area seem to still be present but invisible, as hovering over them causes the appropriate cursor to be shown. This issue is present in Chrome stable 49.0.2623.87 and latest Chromium build (382837). Issue is only present on Macbook Pro retina displays, OR when mirroring the Macbook display to an external display. This has not been observed on any Windows machine or external displays at native resolution, including Apple Cinema displays. Applying transform: translate3d(0,0,0); to the affected element resolves this issue, but is not acceptable as a workaround because we rely on fixed positioning to make a child of this element 'sticky'. Does it occur on multiple sites: N/A Is it a problem with a plugin? N/A Did this work before? Yes Revision 361270 Does this work in other browsers? N/A Chrome version: 49.0.2623.87 Channel: stable OS Version: OS X 10.11.3 Flash Version: Shockwave Flash 21.0 r0 Bisect result: You are probably looking for a change made after 361270 (known good), but no later than 361286 (first known bad). CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/72531bf4c6bd3103da47d6e39784b26df512b8d5..fdc3aee749470b6182f98c07a150e125d60e291c
,
Mar 24 2016
Unable to find the suspect from the above change log, could anyone look in to this issue. Thanks!
,
Mar 24 2016
I'm not familiar with this code, but this commit jumps out at me, any chance it's relevant: https://chromium.googlesource.com/chromium/src/+/01539b801aeca7e811e8441fdfad3011098576dd ? I cloned the source and checked out the commit prior, to try to narrow down which of the commits in the change log's range caused this, but while I can build and run the tip of master just fine, if I try to build the commit prior to the above linked I get the following error: ninja: error: '../../content/browser/resources/net/network_errors_listing.css', needed by 'gen/content/content_resources.pak', missing and no known rule to make it
,
Mar 24 2016
Managed to trim this down to a reproducible case, JSFiddle here: https://jsfiddle.net/gdaolewellman/wuyarn1f/
,
Mar 24 2016
In the JSFiddle above, simply scroll down so that the exclamation point SVG is scrolled off the page, and observe all content disappears.
,
Apr 3 2016
We've seen this as well on several sites, e.g. on http://supqa5.wix.com/gc49hide when scrolling down. Running bisect brought it down to revisions 361270..361286 which include the suspicious commit in comment #3.
,
Apr 11 2016
Remove obsolete component, Blink>Rendering
,
Apr 18 2016
,
May 4 2016
Found another workaround: adding a `z-index:0;` (or any value greater than 0) to gdaolewellman's jsfiddle in either the .b or .c css block causes the d block to render correctly while scrolling.
,
May 4 2016
,
May 5 2016
I can reproduce this on Mac retina / 50.0.2661.94. Cannot reproduce on Mac retina / 51.0.2704.19. Therefore it was fixed sometime between those versions.
,
May 5 2016
Since it'll be fixed in Chrome 51, closing. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by gdaolewe...@gmail.com
, Mar 23 2016