Closed
Bug 119389
Opened 23 years ago
Closed 5 years ago
display= doesn't work if extends= is not present
Categories
(Core :: XBL, defect)
Core
XBL
Tracking
()
RESOLVED
WONTFIX
Future
People
(Reporter: bryner, Unassigned)
Details
(Whiteboard: INVALIDATEME)
Attachments
(1 file)
(deleted),
patch
|
Details | Diff | Splinter Review |
If you use display= on a binding without also using extends=, display= does not
work, i.e.
<binding id="foo" display="xul:outliner"/>
Updated•23 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → Future
this patch just adds a !hasDisplay to the logic so that it doesn't skip in the
case when hasDisplay is true but hasExtends is false.
Comment 3•20 years ago
|
||
My understanding was that this was by design.
Use <binding id="foo" extends="xul:button"> if you don't inherit
Use <binding id="foo" display="xul:button" extends="..."> if you do.
Whiteboard: INVALIDATEME
well in that case can we change the design? Note that even with this patch
<binding id="foo" extends="xul:button"> would still work.
Comment 5•20 years ago
|
||
So, is this a valid bug, or not?
Personally, I would like <binding id="foo" display="xul:outliner"/> to work.
Updated•15 years ago
|
QA Contact: jrgmorrison → xbl
Updated•15 years ago
|
Assignee: hyatt → nobody
Comment 6•15 years ago
|
||
This is a mass change. Every comment has "assigned-to-new" in it.
I didn't look through the bugs, so I'm sorry if I change a bug which shouldn't be changed. But I guess these bugs are just bugs that were once assigned and people forgot to change the Status back when unassigning.
Status: ASSIGNED → NEW
Comment 7•5 years ago
|
||
XBL is now disabled in Firefox (Bug 1583314) and is in the process of being removed from Gecko (Bug 1566221), so closing bugs requesting changes to its implementation as wontfix.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•