Closed
Bug 1224209
Opened 9 years ago
Closed 9 years ago
Header Bar on various website aren't fixed positioned properly and tend to float away or disappear during scrolling
Categories
(Core :: Layout, defect)
Tracking
()
VERIFIED
FIXED
mozilla45
Tracking | Status | |
---|---|---|
firefox44 | --- | unaffected |
firefox45 | --- | verified |
fennec | 45+ | --- |
People
(Reporter: bullionareboy, Assigned: tnikkel)
References
Details
(Keywords: regression)
Attachments
(1 file)
2.06 KB,
patch
|
mattwoodrow
:
review+
|
Details | Diff | Splinter Review |
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
Updated•9 years ago
|
Assignee: nobody → bugmail.mozilla
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 1•9 years ago
|
||
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.
Comment 2•9 years ago
|
||
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.
Keywords: regression
Updated•9 years ago
|
Component: Graphics, Panning and Zooming → Layout
Product: Firefox for Android → Core
Version: Firefox 45 → 45 Branch
Comment 3•9 years ago
|
||
Regressed by bug 1156238; I checked the inbound builds with [1] and without [2] those patches. tn, can you take a look?
[1] http://archive.mozilla.org/pub/mobile/tinderbox-builds/mozilla-inbound-android-api-11/1446537955/
[2] http://archive.mozilla.org/pub/mobile/tinderbox-builds/mozilla-inbound-android-api-11/1446537726/
Blocks: 1156238
Flags: needinfo?(tnikkel)
Updated•9 years ago
|
Assignee: bugmail.mozilla → nobody
Assignee | ||
Comment 4•9 years ago
|
||
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.
Comment 6•9 years ago
|
||
[Tracking Requested - why for this release]: Pretty bad regression. The bug I just duped here was tracking 45+
Comment hidden (typo) |
Comment 9•9 years ago
|
||
*sigh* wrong bug number in the above push. I'll back it out and reland it with the right bug number.
Assignee | ||
Comment 10•9 years ago
|
||
Assignee: nobody → tnikkel
Flags: needinfo?(tnikkel)
Attachment #8687427 -
Flags: review?(matt.woodrow)
Updated•9 years ago
|
Attachment #8687427 -
Flags: review?(matt.woodrow) → review+
Comment 11•9 years ago
|
||
Comment 12•9 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla45
Comment 13•9 years ago
|
||
Assignee | ||
Comment 14•9 years ago
|
||
^-- a reftest
Comment 15•9 years ago
|
||
bugherder |
tracking-fennec: ? → +
tracking-fennec: + → 45+
Comment 16•9 years ago
|
||
Verified as fixed using:
Device: Moto X (Android 4.4)
Build: Firefox for Android 45.0a1 (2015-11-22)
Status: RESOLVED → VERIFIED
Assignee | ||
Comment 17•9 years ago
|
||
(In reply to Kartikaya Gupta (email:kats@mozilla.com) 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.
Description
•