If you use display= on a binding without also using extends=, display= does not
<binding id="foo" display="xul:outliner"/>
I've a patch for this
Created attachment 152402 [details] [diff] [review]
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.
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.
well in that case can we change the design? Note that even with this patch
<binding id="foo" extends="xul:button"> would still work.
So, is this a valid bug, or not?
Personally, I would like <binding id="foo" display="xul:outliner"/> to work.
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.