Hello On several website that tend to use a fixed header bar, the header bar seems to float away from their actual fixed positions upon scrolling the page For example on http://www.theatlantic.com/world/ the jumping header bar issue occurs. And other situation is on http://foxtrotalpha.jalopnik.com/ Here was happens is that the header bar disappears once you scroll down but when you start scrolling up slow/fast you can see the header bar to become visible in a shredded pattern along with the jump. Another site with this problem is http://www.popsci.com/ This was all tested with the FF45(2015-11-12) and Full screen mode enabled
Assignee: nobody → bugmail.mozilla
Status: UNCONFIRMED → NEW
Ever confirmed: true
Investigating these made me realize I screwed up the patch in bug 1214267 so I'll put a follow-up there. However I don't think my screwup is causing this bug, because it happens even with that fixed. It looks like the fixed-pos items aren't generating fixed layers but are getting flattened into the main content layer for some reason, and so we can't move them asynchronously. I'll try to track down a regression range for this.
I bisected fennec nightlies using popsci.com as the test URL. The regression occurred between the nov03 and nov04 nightlies, m-c pushlog range is http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=bb4d614a0b09&tochange=6077f51254c6 It seems to be a layout-side bug because the nov03 layers dump has the fixed-pos layer but the nov04 layers dump doesn't. I'll bisect inbound as well.
Component: Graphics, Panning and Zooming → Layout
Product: Firefox for Android → Core
Version: Firefox 45 → 45 Branch
Regressed by bug 1156238; I checked the inbound builds with  and without  those patches. tn, can you take a look?  http://archive.mozilla.org/pub/mobile/tinderbox-builds/mozilla-inbound-android-api-11/1446537955/  http://archive.mozilla.org/pub/mobile/tinderbox-builds/mozilla-inbound-android-api-11/1446537726/
Looking into this. Interestingly aurora doesn't have this bug, so I was right to go with a more conservative patch for uplift in bug 1199131.
[Tracking Requested - why for this release]: Pretty bad regression. The bug I just duped here was tracking 45+
status-firefox44: --- → unaffected
status-firefox45: --- → affected
tracking-firefox45: --- → ?
Whoops, wrong flag.
tracking-fennec: --- → ?
tracking-firefox45: ? → ---
*sigh* wrong bug number in the above push. I'll back it out and reland it with the right bug number.
Created attachment 8687427 [details] [diff] [review] patch https://treeherder.mozilla.org/#/jobs?repo=try&revision=12fcd48201b7
Assignee: nobody → tnikkel
Attachment #8687427 - Flags: review?(matt.woodrow)
Attachment #8687427 - Flags: review?(matt.woodrow) → review+
Status: NEW → RESOLVED
Last Resolved: 2 years ago
status-firefox45: affected → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla45
^-- a reftest
tracking-fennec: ? → +
tracking-fennec: + → 45+
Verified as fixed using: Device: Moto X (Android 4.4) Build: Firefox for Android 45.0a1 (2015-11-22)
Status: RESOLVED → VERIFIED
status-firefox45: fixed → verified
(In reply to Kartikaya Gupta (email:firstname.lastname@example.org) from comment #9) > *sigh* wrong bug number in the above push. I'll back it out and reland it > with the right bug number. That bug is bug 1214267 for future reference.
You need to log in before you can comment on or make changes to this bug.