Closed
Bug 30519
Opened 25 years ago
Closed 25 years ago
[feature] [XUL] Convert XUL controls array to use XUL widgets (not HTML)
Categories
(Core :: XUL, defect, P3)
Tracking
()
RESOLVED
WONTFIX
M16
People
(Reporter: hyatt, Assigned: hyatt)
Details
(Whiteboard: 1 day)
No description provided.
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M15
Assignee | ||
Updated•25 years ago
|
Summary: [XUL] Convert XUL controls array to use XUL widgets (not HTML) → [feature] [XUL] Convert XUL controls array to use XUL widgets (not HTML)
Updated•25 years ago
|
Whiteboard: 1 day
Comment 2•25 years ago
|
||
Is this part of the skins push? Can't tell, since there is no blurb explaining
it. If so, please add skins keyword and add 29160 in the blocks field.
Assignee | ||
Comment 3•25 years ago
|
||
Marking bug WONTFIX. This capability will come online when/if someone
implements Filters and NodeIterators as per DOM level 2. I don't want to
hack something up that duplicates this capability.
Any code using document.controls must switch to using something else. I will
be removing document.controls completely.
Alec, Ben, sorry, but we shouldn't hack this. It would be wrong.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WONTFIX
Comment 4•25 years ago
|
||
that's fine as long as you realize that we'd be switching to calling
getElementsByTagName() for each type of control.
I'll look at the DOM2 stuff, just because I'm curious what it is.
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: jrgmorrison → xptoolkit.widgets
You need to log in
before you can comment on or make changes to this bug.
Description
•