Closed
Bug 334452
Opened 19 years ago
Closed 12 years ago
E4X: not displaying proper xmlns in node.toXMLString()
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: BijuMailList, Unassigned)
References
Details
(Keywords: testcase)
Attachments
(1 file)
(deleted),
text/html
|
Details |
E4X: not displaying proper xmlns in node.toXMLString()
a=<a xmlns:n="uri.X"></a>;
m=new Namespace('m',"uri.A")
a.m::b="x";
a.*::b.toXMLString()
give ==>
<m:b xmlns:n="uri.X">x</m:b>
expected ==>
<m:b xmlns:m="uri.A">x</m:b>
steps:-
1. open attachment no_xmlns.html
2. click link Input Case : "0"
3. click "test"
4. repeat for 1 and 2
Comment 2•19 years ago
|
||
Biju, please feel free to file bugs as NEW, not UNCONFIRMED. Thanks,
/be
Status: UNCONFIRMED → NEW
Ever confirmed: true
(In reply to comment #2)
> Biju, please feel free to file bugs as NEW, not UNCONFIRMED. Thanks,
Sure, thanks
Comment 4•17 years ago
|
||
This may be related. If you browse to an XML file, eg
https://wayf.incommonfederation.org/InCommon/InCommon-metadata.xml
it renders without xmlns tags. If you view the source, they're in there!!!
Here's a simpler example, paste this into a file and browse to it:
<XmlDoc xmlns="myns" />
Comment 5•17 years ago
|
||
Gabriel: your comment does not seem to have anything to do with E4X (ECMAScript for XML). Why did you add it to this bug?
/be
unrelated to above comments...
minor correction...
expected should be ==>
<m:b xmlns:m="uri.A" xmlns:n="uri.X">x</m:b>
Comment 7•17 years ago
|
||
Brendan,
I'm sorry. I didn't know where else to log it. Perhaps it's a new bug. I tried to find something related to "xmlns".
When Firefox browses an XML file, does it use E4X? (or conversely, does E4X use some of the same toXMLString() code?)
Should I open a new bug?
Gabriel
Comment 8•17 years ago
|
||
Gabriel: no (no) and yes.
/be
Comment 9•12 years ago
|
||
E4X will be removed again from Spidermonkey (bug 788293)
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•