Jason Orendorff [:jorendorff] Assignee
	Description • 12 years ago

Finish disabling E4X for web content.

	Jason Orendorff [:jorendorff] Assignee
	Comment 1 • 12 years ago

Running against Try Server now.

	Jorge Villalobos [:jorgev] (he/him)
	Comment 2 • 12 years ago

Adding add-on compat and dev-doc flags so that we document this when it lands.

	David Mandelin [:dmandelin]
	Comment 3 • 12 years ago

How'd the try server run go?

	Jason Orendorff [:jorendorff] Assignee
	Comment 4 • 12 years ago

Sorry I didn't respond to this at the time! I thought I had. The Try Server results were lost when (at some point) the whole Try Server system had to be restarted (around the time of comment 1, there were some Try Server Troubles).

I just pushed to try again, not noticing that we're perma-orange on Mac right now--but the results on the other platforms will still be useful:
https://tbpl.mozilla.org/?tree=Try&rev=9653a0823eb5

	Jason Orendorff [:jorendorff] Assignee
	Comment 5 • 12 years ago

Ah, there was a new test that mentioned XML. Easily patched.

	Jeff Walden [:Waldo]
	Comment 6 • 12 years ago

Comment on attachment 655395 [details] [diff] [review]
v2

You had me at +pref("javascript.options.xml.content", false);.

	Ryan VanderMeulen [:RyanVM]
	Comment 7 • 12 years ago

https://hg.mozilla.org/mozilla-central/rev/6564c3183a04

	David Mandelin [:dmandelin]
	Comment 8 • 12 years ago

Yay!

	Tom S [:evilpie]
	Comment 9 • 12 years ago

Was already mentioned at
https://developer.mozilla.org/en-US/docs/Firefox_17_for_developers
Made the message in https://developer.mozilla.org/en-US/docs/E4X a little bit more clear.