Closed
Bug 62783
Opened 24 years ago
Closed 24 years ago
Implement default content in <children>
Categories
(Core :: XBL, enhancement, P3)
Core
XBL
Tracking
()
RESOLVED
FIXED
mozilla0.9
People
(Reporter: dr, Assigned: hyatt)
References
Details
(Whiteboard: [xbl1.0])
Attachments
(2 files)
(deleted),
patch
|
Details | Diff | Splinter Review | |
(deleted),
patch
|
Details | Diff | Splinter Review |
When no <children> tag is given in the content for a binding, either all of the
content is substituted (when the bound element has no children) or none of it is
(when the bound element does have children). This concept of default anonymous
content is useful. But when a <children> tag *is* given, there is no way to
specify default content for when the bound element has no kids. So we want to
implement the following syntax:
<content>
<!-- ... -->
<children>
<!-- default anonymous content, for if the bound element has no kids -->
</children>
<!-- ... -->
</content>
This lets us make buttons *always* have fancy borders (like the modern skin's 3d
effects) regardless of whether the button has content, or just a value
attribute; likewise, menuitems can have hyatt's Dancing Pandas (tm) without
sacrificing all the other fun chrome that goes along with being a menuitem.
adding bug 55292 as dependency. not necessarily true, but hey, it'd be nice to
have that working before this...
Assignee | ||
Comment 4•24 years ago
|
||
I need this to implement the simplified tree syntax (see the bug on converting
<tree> to <listbox>). Pulling in.
Target Milestone: Future → mozilla0.9
Assignee | ||
Comment 5•24 years ago
|
||
Assignee | ||
Comment 6•24 years ago
|
||
Ready for r and sr.
Assignee | ||
Comment 7•24 years ago
|
||
Comment 8•24 years ago
|
||
looks good, sr=waterson
Assignee | ||
Comment 9•24 years ago
|
||
Fixed.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•