Closed
Bug 858181
Opened 12 years ago
Closed 12 years ago
Regression: Position fixed footer on Duck Duck Go floats above other content
Categories
(Firefox for Android Graveyard :: Toolbar, defect)
Tracking
(firefox22 affected, firefox23 affected)
RESOLVED
DUPLICATE
of bug 856497
People
(Reporter: aaronmt, Unassigned)
References
()
Details
(Keywords: regression, reproducible)
Attachments
(1 file)
(deleted),
image/png
|
Details |
http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=44cf42a8e6e5&tochange=15e82d1c776a
This looks to be a regression from http://hg.mozilla.org/integration/mozilla-inbound/rev/d91a87b222e4 via bug 853831
See attached screenshot (steps, simply visit http://www.duckduckgo.com)
--
Nightly/Aurora (04/04)
LG Nexus 4 (Android 4.2.2)
Reporter | ||
Comment 1•12 years ago
|
||
Screenshot at the time of filing on Nightly (04/04)
Reporter | ||
Comment 2•12 years ago
|
||
For the other layout issue regarding the search button, see bug 841363
Comment 3•12 years ago
|
||
To clarify, the bug here isn't that the bar is above the text box (which would happen, looking at the page structure), but that it's higher than it should be (which shouldn't happen - the position:fixed bar is aligned to the bottom). There's a chance this could be to bug 856932, but I have a hard time duplicating it on the razri.
There seems to be other badness going on on this page where the bottom bar turns invisible... I'm not sure if this is JS doing this, gfx bugs, layout bugs... Possibly JS scrolling isn't affecting fixed margins correctly?
Some break down of the issues on this page, with consistent STR would be good.
Flags: needinfo?(aaron.train)
Comment 4•12 years ago
|
||
Argh, so it seems that the fixed margins don't always change correctly when the page changes size, which is likely causing some of the badness on this site (and is causing badness on another bug I'm trying to fix...) - I'll fix that as part of this bug.
Updated•12 years ago
|
Flags: needinfo?(aaron.train)
Comment 5•12 years ago
|
||
Just tested, this same bug exists on FirefoxOS, but I think they use this same code now? (it used to be duplicated elsewhere in the tree, but I can't remember off-hand where that was)
Adding needinfo?benfrancis (if you don't know, please pass it on to someone that might :))
This is a really low-risk, high-impact fix, let's uplift it wherever we can.
Assignee: nobody → chrislord.net
Status: NEW → ASSIGNED
status-b2g18:
--- → affected
status-b2g18-v1.0.0:
--- → affected
status-b2g18-v1.0.1:
--- → affected
tracking-b2g18:
--- → ?
Component: Graphics, Panning and Zooming → Graphics: Layers
Flags: needinfo?(bfrancis)
Product: Firefox for Android → Core
Comment 6•12 years ago
|
||
Argh, wrong bloody tab...
Assignee: chrislord.net → nobody
Status: ASSIGNED → NEW
status-b2g18:
affected → ---
status-b2g18-v1.0.0:
affected → ---
status-b2g18-v1.0.1:
affected → ---
tracking-b2g18:
? → ---
Component: Graphics: Layers → Graphics, Panning and Zooming
Flags: needinfo?(bfrancis)
Product: Core → Firefox for Android
Comment 7•12 years ago
|
||
The possibility of the bar not being attached to the bottom will be fixed by the patch I just attached to bug 856497. That it's above content in terms of z-ordering is down to the page, so I'm duping this (but please reopen if you think I'm wrong).
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Updated•11 years ago
|
tracking-fennec: ? → ---
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•