Issue 30975 - chromium - Implement E4X Support for scripts and extensions - An open-source project to help move the web forward.

Issue 30975:	Implement E4X Support for scripts and extensions
	19 people starred this issue and may be notified of changes.	Back to list

Status:	Duplicate
Owner:	----
Closed:	May 2010
Type-Feature Pri-3 Cr-Internals

Restricted

Only users with Commit permission may comment.

Reported by [email protected], Dec 21, 2009

Chrome Version       : 4.0.266.0 (Official Build 33992)
URLs (if applicable) : http://en.wikipedia.org/wiki/E4X
https://developer.mozilla.org/en/e4x
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
     Safari 4: FAIL
  Firefox 3.x: OK
         IE 7: FAIL
         IE 8: FAIL

This bug is to track the progress of E4X implementation, allowing 
Greasemonkey scripts which use it to be run in Chromium.

Dec 24, 2009

#1 [email protected]

Finally, someone noticed! I have been waiting for E4X support in Chrome since the very 
first version. E4X is such a critical feature which makes development so much simpler. 
E4X has been there since Firefox 1.5 and I simply cant wait to have its support in 
Chrome. Please don't let it die. If E4X isn't supported in another major browser, we 
wont be seeing it used in any web development project.

Dec 30, 2009

#2 robinwinslowmorris

please support e4x?

Dec 30, 2009

#3 robinwinslowmorris

Why is this still "unconfirmed"? It's definitely true.
Support for the latest ECMAScript standard should be higher priority. It's not like 
it's new - it's been around since 2005:
http://www.ecma-international.org/publications/standards/Ecma-357.htm

Dec 30, 2009

#4 [email protected]

Is there some chromium developer forum we can post this so that web developers know
that this issue is being raised and they can vote to do something about it? I am sure
this issue will get many votes when devs become aware of it.

Dec 30, 2009

#5 [email protected]

See also https://code.google.com/p/v8/issues/detail?id=235 as E4X is an ECMAScript 
extension, it will need to be implemented in V8 (the JavaScript engine) rather than 
Chromium.

Feb 18, 2010

#6 [email protected]

Using an automated filter to classify this issue into an area...gulp

Labels: -Area-Undefined Area-WebKit autoclass

Feb 19, 2010

#7 [email protected]

(No comment was entered for this change.)

Labels: -autoclass -Area-WebKit Area-Undefined

Mar 28, 2010

#8 cfinke

E4X support would make my porting of ScribeFire to Chrome much easier.

Apr 9, 2010

#9 [email protected]

There ius a good summary of why E4X makes a lot of sense here :
http://www.theopensourcery.com/keepopen/?p=2157
I am afreaid E4x is at a tipping point if Chrome or IE9 don't do it some great code
is lost - in French the expression is C'est dommage.

May 10, 2010

#10 [email protected]

Beside server side uses, e4x would also handle client side SVG needs quite nice too.

May 11, 2010

#11 [email protected]

This is a dupe of v8 bug: https://code.google.com/p/v8/issues/detail?id=235

Status: Duplicate
Labels: -Type-Bug -Pri-2 -Area-Undefined Type-Feature Pri-3 Area-Internals

Oct 12, 2012

#12 [email protected]

This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.

Labels: Restrict-AddIssueComment-Commit

Mar 10, 2013

#13 [email protected]

(No comment was entered for this change.)

Labels: -Area-Internals Cr-Internals

► Sign in to add a comment