Created attachment 8826363 [details] Reduced testcase User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:53.0) Gecko/20100101 Firefox/53.0 Build ID: 20170112030301 Steps to reproduce: 1. Ensure e10s is active. 2. Open testcase in large/maximized window. 3. Scroll down. Actual results: With e10s enabled, the hidden overflow appears as a flickering black rectangle while scrolling. This does not happen with e10s disabled. Expected results: No flickering black rectangle should appear.
Bug is reproducible on latest Nightly x64 on Windows 10, and Firefox 50.1.0 on macOS 10.12.2.
disabled apz seems to fix the problem
I can repro this (on Windows), looks pretty bad. Happens even when keyboard scrolling. There's a bunch of 3D stuff here which I'm not too familiar with. CC'ing botond and matt who might have more knowledge/time to look into this.
Thanks for tracking that down! Thinker, can you look into this?
I will look into this bug in following days.
Any updates on this, Thinker?
Sorry! I am busy on some other tasks. I will try to fix this bug in next week.
Too late for firefox 52, mass-wontfix.
Kats, Milan, any thoughts here? Should this be a priority to fix for 55 or do we want to treat it as backlog that would be nice to have fixed someday? We don't have duplicate reports, so I'm not sure how common this issue might be.
Yeah I haven't seen any other reports of this either. Thinker, will you have any time to look into this in the next month or so?
I can no longer reproduce the problem on Nightly55.0a1. This seems to be fixed. Fixed range: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=00a166a8640dffa2e0f48650f966d75ca3c1836e&tochange=0d6ffde320ec3a3b44dc4c27f7c11cc9a9bf341c https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=f0d0fa45265951efd27c283784a94ebfee2f957d&tochange=58181c34aa51b2aa8e129c0ec5c831d0a877e00f Fixed by: Bug 1352442
Thanks Alice! Marking as fixed via bug 1352442.
Probably better to let bug 1352442 ride the trains so any fallout from that change has time to be found, given that this is a pretty low-impact bug.
I believe this bug has been fixed only partially. Since the STR are different, I have filed a new bug for this: bug 1360952.