User Agent: Mozilla/5.0 (Windows NT 6.0) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.64 Safari/537.11
Steps to reproduce:
The EX4 doc page https://developer.mozilla.org/en-US/docs/E4X says:
" E4X is deprecated. It will be disabled by default for content in Firefox 16, disabled by default for chrome in Firefox 17, and removed in Firefox 18. "
But the Firefox 17 for developers https://developer.mozilla.org/en-US/docs/Firefox_17_for_developers says:
"Disabled E4X for web content by default"
And I see it still working for chrome in release 18.0a2
So... what is it ?
I got a bit confused...
I should have been enlightened... ;)
The basic gist of things as far as this goes is that we weren't able to stick exactly to the initially-planned schedule. E4X is on its way out -- just not on the original 16/17/18 schedule. I'm not entirely sure what the actual schedule is now, nor do I really know exactly what the schedule we've actually followed thus far is. CCing someone who knows this better than I do, who can hopefully update the pages you mention to be correct (as far as we know at the current time, at least, modulo schedule slippage).
e4x has now been removed (bug 788293) and https://developer.mozilla.org/en-US/docs/E4X now says:
"Warning: E4X is obsolete. It has been disabled by default for webpages (content) in Firefox 17, disabled by default for chrome in Firefox 20, and will be removed in Firefox 21. Use DOMParser/DOMSerializer or a non-native JXON algorithm instead."
All is well here.