Closed
Bug 1497762
Opened 6 years ago
Closed 6 years ago
Fixed-position footer on KQED snaps upwards from bottom of viewport when you scroll to bottom of page
Categories
(Core :: Panning and Zooming, defect, P3)
Core
Panning and Zooming
Tracking
()
VERIFIED
DUPLICATE
of bug 1495055
People
(Reporter: dholbert, Unassigned)
References
Details
(Keywords: regression)
Attachments
(1 file)
5.27 MB,
video/mp4
|
Details |
STR: 1. Visit https://www.kqed.org/radio/program/live-from-here-highlights in Firefox Nightly for Android. 2. Wait for the page to finish loading, as reported by the throbber bar. (might take a few seconds for ads/etc to finish loading) 3. Scroll to the bottom of the page. ACTUAL RESULTS: The "Play|Trending|Search" footer bar snaps upwards a few pixels (leaving awkward dead space at the bottom). EXPECTED RESULTS: That footer bar should remain snapped to the bottom of the viewport. It's styled as "position:fixed; top:auto; bottom:0", so it should stay at the bottom. mozregression gives me this regression range: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=2d1d32212c1e4107bef4d24dbbe2f12adca11837&tochange=77433149bfdcc82287acaed94b942818785b556e In that range, it looks like bug 1465616 is the likely culprit. (Looking at that bug, it's possible this is a dupe of bug 1495055, but we'll see when its patch re-lands I guess... for now, tentatively marking bug 1495055 as a dependency, since it seems likely it'll help here.)
Reporter | ||
Comment 1•6 years ago
|
||
Comment 2•6 years ago
|
||
This is fixed by the updated patch in bug 1495055; marking as a dupe.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 3•6 years ago
|
||
That's great to hear! Thanks. (I'll remove that bug from the dependency field, too, then.)
No longer depends on: 1495055
Reporter | ||
Comment 4•6 years ago
|
||
Just verified that I can't reproduce this in Nightly on Android anymore (which makes sense, since the dupe-target bug's patch has landed). --> Marking as a verified dupe.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•