Using just "CreateElement()" will break as soon as someone uses something besides XUL for the default namespace. Use "CreateElementWithNameSpace()" instead.
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → INVALID
I manually set the namespace via SetNameSpace.
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.
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?
Clearing Invalid resolution due to reopen.
I don't make HTML or XUL content nodes. I use XML nodes... And it seems to work fine. Am I missing something?
Status: REOPENED → RESOLVED
Last Resolved: 19 years ago → 19 years ago
Resolution: --- → FIXED
Ok, that's fine then.
Chris, could you verify this? Thanks! -Chris
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.