Closed
Bug 1939891
Opened 9 months ago
Closed 9 months ago
Allow remaining hard-coded XUL frames (like <xul:image>) to be out of flow.
Categories
(Core :: Layout, defect)
Core
Layout
Tracking
()
RESOLVED
FIXED
135 Branch
People
(Reporter: emilio, Assigned: emilio)
References
Details
Attachments
(1 file)
I was confused as for why bug 1933479 couldn't position the icon using absolute positioning or what not. It's just because of legacy reasons.
| Assignee | ||
Comment 1•9 months ago
|
||
Just like their HTML counterparts. The only reason they couldn't in the
past was because they were using XUL layout, but that is long gone and
now things like <browser> use nsSubDocumentFrame, <image> uses
nsImageFrame etc. Relevant HTML counter-parts like <img> do support
this.
Let me know if you want to add a test for this, but it's just removing
legacy special cases so I'd rather avoid it if I can :)
Updated•9 months ago
|
Assignee: nobody → emilio
Status: NEW → ASSIGNED
Pushed by ealvarez@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/97a3c0a8019f
Allow remaining hard-coded XUL frames to be out of flow. r=layout-reviewers,AlaskanEmily
Comment 3•9 months ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 9 months ago
status-firefox135:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 135 Branch
| Assignee | ||
Comment 4•9 months ago
|
||
Can we back this out of beta for causing bug 1940698?
Flags: needinfo?(sheriffs)
Comment 5•9 months ago
|
||
Backed out from beta: https://hg.mozilla.org/releases/mozilla-beta/rev/144219de44658ae48bbe6692e7f97729b31f72f1
Flags: needinfo?(sheriffs)
Updated•9 months ago
|
status-firefox135:
fixed → ---
status-firefox136:
--- → fixed
Target Milestone: 135 Branch → 136 Branch
Updated•9 months ago
|
status-firefox135:
--- → disabled
Target Milestone: 136 Branch → 135 Branch
Updated•9 months ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•