According to Mozilla’s Dave Mandelin, E4X is deprecated and “will be disabled by default for content in Firefox 16, disabled by default for chrome in Firefox 17, and removed in Firefox 18”.
As an alternative, Mozilla suggests using DOMParser / DOMSerializer or a non-native JXON algorithm instead.
On a positive note, it will accelerate the development process and minimize security risks, so that can’t be bad, right?
About (Author Profile)
Vygantas is a former web designer whose projects are used by companies such as AMD, NVIDIA and departed Westood Studios. Being passionate about software, Vygantas began his journalism career back in 2007 when he founded FavBrowser.com. Having said that, he is also an adrenaline junkie who enjoys good books, fitness activities and Forex trading.