Investigate using <toolbox> as an HTML element
Categories
(Toolkit :: UI Widgets, task)
Tracking
()
People
(Reporter: ntim, Unassigned)
References
(Depends on 3 open bugs, Blocks 1 open bug)
Details
Attachments
(2 obsolete files)
It would be nice to see what's missing/required when we switch over from XULElement to HTMLElement, and <toolbox> would be a great candidate for experimentation given the low number of usages and since it's not tied to many XUL features (flex/orient attributes, splitter, etc).
Reporter | ||
Comment 1•5 years ago
|
||
Reporter | ||
Comment 2•5 years ago
|
||
Comment 3•5 years ago
|
||
This is a variation on the other patch in the bug, where we turn it into a Custom
Element in order to support common xul element properties (.flex, .hidden, etc).
This depends on the patch in Bug 1592369 which moves some of the xul flex attributes
into CSS
Depends on D51013
Updated•5 years ago
|
Updated•5 years ago
|
Comment 4•3 years ago
|
||
The following patch is waiting for review from an inactive reviewer:
ID | Title | Author | Reviewer Status |
---|---|---|---|
D51168 | Bug 1580983 - Investigate porting <xul:toolbox> to <html:moz-toolbox> custom element | bgrins | Gijs: Resigned from review |
ntim: Resigned from review |
:bgrins, could you please find another reviewer or abandon the patch if it is no longer relevant?
For more information, please visit auto_nag documentation.
Updated•3 years ago
|
Comment 5•3 years ago
|
||
Abandoned it as I don't have immediate plans to work on this - I think the patch could be picked back up if/when we prioritize work on Bug 1563415
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Description
•