Closed
Bug 353349
Opened 18 years ago
Closed 18 years ago
Implement nsSVGDocument::GetDefaultNamespaceID
Categories
(Core :: SVG, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: tor, Assigned: tor)
Details
Attachments
(1 file)
|
1.90 KB,
patch
|
bzbarsky
:
review-
bzbarsky
:
superreview-
|
Details | Diff | Splinter Review |
I think this was an accidental omission rather than intentional.
Attachment #239191 -
Flags: superreview?(roc)
Attachment #239191 -
Flags: review?(bzbarsky)
|
||
Comment 2•18 years ago
|
||
I believe this was quite purposeful. That is, we do NOT want createElement in SVG documents creating SVG-namespaced elements. There was a good bit of discussion about it in a bug at some point, as I recall.
|
|
||
Comment 3•18 years ago
|
||
See bug 236408 comment 25, to be exact.
Looking at DOM2/3 core, it does seem that the namespace should be null. Should the nsXULDocument::GetDefaultNamespaceID method be removed or nsDocument::CreateElement modified to always use kNameSpaceID_None?
|
|
||
Comment 5•18 years ago
|
||
Do read bug 236408, esp around comment25 . We'd break the world (like all of our chrome and all extensions) if we changed what XUL does. :( So we violate the DOM spec there (either for now, or permanently, depending on what we want to do with Gecko 2). We violate it in so many other ways in XUL that it really doesn't matter much....
Bleh.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WONTFIX
|
|
||
Updated•18 years ago
|
Attachment #239191 -
Flags: superreview?(roc)
Attachment #239191 -
Flags: superreview-
Attachment #239191 -
Flags: review?(bzbarsky)
Attachment #239191 -
Flags: review-
You need to log in
before you can comment on or make changes to this bug.
Description
•