The default bug view has changed. See this FAQ.

enable @supports rule in all builds

RESOLVED FIXED in mozilla22

Status

()

Core
CSS Parsing and Computation
P3
normal
RESOLVED FIXED
4 years ago
3 years ago

People

(Reporter: dbaron, Assigned: dbaron)

Tracking

({dev-doc-complete})

Trunk
mozilla22
dev-doc-complete
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

4 years ago
Currently @supports rules are enabled for nightly/aurora versions but not for beta/release versions.  Given that the spec is going to CR very soon (and should be by the time current nightly gets to beta), we should enable it for all builds so that we ship it.

I don't see any known issues that should block us from doing this.  (I don't see any valid issues remaining in bug 780060 or bug 816045.)

But I probably ought to check the current test suite submissions.
(Assignee)

Comment 1

4 years ago
Created attachment 730335 [details] [diff] [review]
Turn on @supports in release builds.
Attachment #730335 - Flags: review?(cam)
Comment on attachment 730335 [details] [diff] [review]
Turn on @supports in release builds.

r=me if you're happy with how we fare on any @supports tests we haven't yet imported from the official test suite.
Attachment #730335 - Flags: review?(cam) → review+
(Assignee)

Comment 3

4 years ago
https://hg.mozilla.org/integration/mozilla-inbound/rev/b2f950261473

I still need to go through the tests, though.
https://hg.mozilla.org/mozilla-central/rev/b2f950261473
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla22

Comment 5

4 years ago
Could someone update the realese notes?
https://www.mozilla.org/en-US/firefox/22.0beta/releasenotes/
(Assignee)

Comment 6

4 years ago
I don't think this belongs in the release notes, but it does belong in developer documentation.
Keywords: dev-doc-needed
(Assignee)

Comment 7

4 years ago
In Opera's tests, we fail at-supports-014, which is incorrect as described here (with patch):
http://lists.w3.org/Archives/Public/public-css-testsuite/2013May/0019.html

and we fail 4 items in contributors/opera/submitted/css3-conditional/js/001.html .  I again think the test is invalid, as described here:
http://lists.w3.org/Archives/Public/public-css-testsuite/2013May/0020.html
Target Milestone: mozilla22 → ---
(Assignee)

Updated

4 years ago
Target Milestone: --- → mozilla22
Updated:
https://developer.mozilla.org/en-US/docs/Web/API/CSS.supports
https://developer.mozilla.org/en-US/docs/Web/API/CSS
https://developer.mozilla.org/en-US/docs/Web/CSS/@supports
and 
https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/22 (on by default)
Keywords: dev-doc-needed → dev-doc-complete
Blocks: 864005
You need to log in before you can comment on or make changes to this bug.