Closed
Bug 426197
Opened 17 years ago
Closed 17 years ago
Gecko 1.9 adds unrequired and wrong xmlns to generates XML tags
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
DUPLICATE
of bug 393192
People
(Reporter: helios, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b4) Gecko/2008030318 Firefox/3.0b4
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b4) Gecko/2008030318 Firefox/3.0b4
The current Gecko 1.9 engine as in Firefox 3.0b4 adds unrequired and wrong xmlns to generates XML tags. This becomes an issue as libraries as JSJaC add those xmlns values after creating the tag, so that Firefox already set an empty xmlns and thus setting it to a meaningful value fails. Additionally, this generated problems since it adds xmlns tags where none are required. The impact on libraries like JSJaC is pretty fatal, for example, you can see in JWChat that nothing works the way it's supposed to do anymore.
Reproducible: Always
Steps to Reproduce:
1.launch jwchat
2.look at the produced XML
3.You only see XML in debug mode, so please contact me if you need an installed JWchat in debug mode
Actual Results:
Gecko inserts useless and wrong xmlns to tags.
Expected Results:
It should just behave like in 1.8 and let adding xmlns be the javascript developers' problem.
| Reporter | ||
Comment 1•17 years ago
|
||
Version is 3.0b4, though I selected trunk. 3.0b4's missing there.
Updated•17 years ago
|
Component: General → DOM
Product: Firefox → Core
QA Contact: general → general
Version: unspecified → Trunk
Comment 2•17 years ago
|
||
The xml namespace must be set when creating an element using createElementNS. It cannot be modified after the fact by adding an xmlns attribute. The xmlns attribute is not a real attribute, it only exists in the serialised form of xml.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
| Reporter | ||
Comment 3•17 years ago
|
||
Gecko 1.9 inserts an empty xmlns when using createElement. createElementNS seems to work fine.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Updated•17 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago → 17 years ago
Resolution: --- → DUPLICATE
| Assignee | ||
Updated•7 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•