Closed
Bug 855455
Opened 12 years ago
Closed 12 years ago
enable @supports rule in all builds
Categories
(Core :: CSS Parsing and Computation, defect, P3)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
FIXED
mozilla22
People
(Reporter: dbaron, Assigned: dbaron)
References
Details
(Keywords: dev-doc-complete)
Attachments
(1 file)
990 bytes,
patch
|
heycam
:
review+
|
Details | Diff | Splinter Review |
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•12 years ago
|
||
Attachment #730335 -
Flags: review?(cam)
Comment 2•12 years ago
|
||
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•12 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/b2f950261473
I still need to go through the tests, though.
Comment 4•12 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla22
Could someone update the realese notes?
https://www.mozilla.org/en-US/firefox/22.0beta/releasenotes/
Assignee | ||
Comment 6•12 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•11 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•11 years ago
|
Target Milestone: --- → mozilla22
Comment 8•11 years ago
|
||
Updated•11 years ago
|
Keywords: dev-doc-needed → dev-doc-complete
You need to log in
before you can comment on or make changes to this bug.
Description
•