Closed
Bug 9465
Opened 25 years ago
Closed 25 years ago
use CreateElementWithNameSpace() for anonymous content nodes
Categories
(Core :: XUL, defect, P3)
Core
XUL
Tracking
()
VERIFIED
FIXED
M9
People
(Reporter: waterson, Assigned: eric)
Details
(Whiteboard: Back to engineer for verification...)
Using just "CreateElement()" will break as soon as someone uses something besides XUL for the default namespace. Use "CreateElementWithNameSpace()" instead.
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M9
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
Assignee | ||
Comment 1•25 years ago
|
||
I manually set the namespace via SetNameSpace.
Updated•25 years ago
|
Status: RESOLVED → REOPENED
Comment 2•25 years ago
|
||
That won't work right for HTML content. You need to get the namespace right up front. I use this in nsMenuFrame.cpp when I make anonymous content. It's trivial for you to look at that and use it as a guide for switching your stuff over.
Reporter | ||
Comment 3•25 years ago
|
||
Eric and I talked about this. In his case, I think it's okay for him to manually create XML nodes (_not_ XUL nodes), and then just twiddle them himself. Eric, this is what you're doing, isn't it?
Assignee | ||
Comment 5•25 years ago
|
||
I don't make HTML or XUL content nodes. I use XML nodes... And it seems to work fine. Am I missing something?
Updated•25 years ago
|
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
Comment 6•25 years ago
|
||
Ok, that's fine then.
Updated•25 years ago
|
Whiteboard: Back to engineer for verification...
Comment 7•25 years ago
|
||
Chris, could you verify this? Thanks! -Chris
Reporter | ||
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
BULK MOVE: Changing component from XUL to XP Toolkit/Widgets: XUL. XUL component will be deleted.
Component: XUL → XP Toolkit/Widgets: XUL
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: ckritzer → xptoolkit.widgets
You need to log in
before you can comment on or make changes to this bug.
Description
•