Bug 5381 – Support E4X

• Status: RESOLVED
• Resolution: WONTFIX
• Component: JavaScriptCore

[Arthur Langereis]

JavaScriptCore should support E4X.

[Joost de Valk (AlthA)]

Reassigning to webkit-unassigned, to make sure more people see this.

[Joost de Valk (AlthA)]

Sounds like a valid request.

[Frederick C. Lee]

I'm an OS X developer hired to add OS X support to a MS product, here in Silicon Valley, CA.  XML is the data vector between the two worlds.  I *NEED* E4X support in Safari.  

Firefox appears to be the ONLY browser that supports E4X:

var e = <employees> 
 <employee id="1"><name>Joe</name><age>20</age></employee> 
 <employee id="2"><name>Sue</name><age>30</age></employee> 
</employees>; 
 
var names = e..name;  // get all the names in e 


Safari can't handle the above code.
Firefox/Mozilla can.

Apple claims Safari is the *best* browser.

WHERE'S E4X?????

Ric.
[e-mail]

[Mark Rowe (bdash)]

Please leave the rhetoric out of comments in Bugzilla.  It detracts from the technical nature of the content.

[Marcel]

Can someone outline a reason why this isn't a major priority?

e4x is the best thing to happen to JavaScript, especially server-side implementations, what are the politics behind it not being included? I guess I am trying to understand both, is it still not on the roadmap, and why not.

Thank you for your time,
Marcel

[Robin]

Is there no way to vote on bugs? Why is support for the latest ECMAScript standard not higher priority - why has this still not been assigned to anyone?

[Mark Rowe (bdash)]

*** Bug 34678 has been marked as a duplicate of this bug. ***

[Robert]

I to would like to vote for webkit to have e4x. It would be so much fun having it.

[Alex Milowski]

Just for reference, this is ECMA Standard 357, ECMAScript for XML (E4X) Specification, 2nd Edition (December 2005)

http://www.ecma-international.org/publications/standards/Ecma-357.htm

[Anders Carlsson]

E4X has been removed from Firefox so I don't see the point in us supporting it, let's close this bug.