Closed Bug 753542 Opened 9 years ago Closed 9 years ago
.options .xml .content and .chrome)
No description provided.
The problem is that JSOPTION_XML doesn't do what you might guess, so I'm splitting it into two separate options: JSOPTION_ALLOW_XML - if this is off, we won't allow E4X syntax no matter what your version number is JSOPTION_MOAR_XML - if ALLOW_XML is off, this has no effect; if ALLOW_XML is on, this has the effect of the existing JSOPTION_XML flag, which means we allow E4X even in JS version numbers that don't normally have it, and <!-- is treated as an E4X comment rather than as a // to-end-of-line comment. This patch simply renames the existing JSOPTION_XML to JSOPTION_MOAR_XML, and a few other trivial renamings/cleanups. There should be no change in behavior.
Assignee: general → jorendorff
Adds JSOPTION_ALLOW_XML and unconditionally turns it on throughout the browser (and JS test suites except jsapi-tests).
Oh - I should add that due to bugs in part 2, this isn't passing tests yet. At the moment, it's disabling XML support more than it should. Just putting the patches up early so anyone interested could look into the effect on addons.
Sorry for the last-minute request. I'd like addon developers to be able to test their stuff using FF15 this release, and default the pref to false in FF16.
New Try run, since I added code: https://tbpl.mozilla.org/?tree=Try&rev=b96dd38052fa
Attachment #628773 - Flags: superreview?(jst) → superreview+
Thank you for the rapid reviews! https://hg.mozilla.org/integration/mozilla-inbound/rev/ce0c716baefd
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla16
You need to log in before you can comment on or make changes to this bug.