Should we be disabling @supports? What criteria are we using to determine if it's safe to let through to Beta?
I think we shouldn't ship it in Beta if we don't plan to ship it in final. So for 17, I think we should pref off, personally.
Comment on attachment 665207 [details] [diff] [review] patch to flip the pref to false r=me, for aurora; let's keep this on m-c for now.
Comment on attachment 665207 [details] [diff] [review] patch to flip the pref to false [Approval Request Comment] Bug caused by (feature/regressing bug #): 649740 User impact if declined: We'd be violating our commitment to pref off features from pre-CR specs. Testing completed (on m-c, etc.): No testing, it's just a pref flip. Risk to taking this patch (and alternatives if risky): Low. String or UUID changes made by this patch: N/A
Comment on attachment 665207 [details] [diff] [review] patch to flip the pref to false Please make sure to land before Monday (to make the merge) and please mark bug 649740 as "disabled" for status-firefox17 when this lands.
Docs probably need to be updated to mention that it is preffed off for Firefox 17.
Backed out for orange; the tests need tweaking so they don't fail when the pref is off: https://hg.mozilla.org/releases/mozilla-aurora/rev/40414595ae48
Both: https://developer.mozilla.org/en-US/docs/CSS/@supports and https://developer.mozilla.org/en-US/docs/Firefox_17_for_developers are up-to-date with the disabling (and the pref).
It's not up-to-date for release notes: http://www.mozilla.org/en-US/firefox/17.0a2/auroranotes/
Should do 18 as wel.