Closed Bug 1513643 Opened 10 months ago Closed 4 months ago
Enable @supports selector() by default
I see no reason not to, since everyone agreed on the feature.
I don't see a reason not to, since everyone agreed on it spec-wise.
Has the CSS WG explicitly cleared this to ship?
(In reply to David Baron :dbaron: 🏴 ⌚UTC-8 (if account gets disabled due to email bounces, ask a bugzilla admin to reenable it) from comment #2) > Has the CSS WG explicitly cleared this to ship? No, I don't think explicitly no. Happy to wait or whatever you think it's needed for that.
So I think we need to: 1. actually write a spec for it; I volunteered to do that at TPAC but haven't gotten to it yet. If you'd like to take a shot at it I'm happy to provide some guidance. 2. Then suggest to the WG that we'd like to ship. It might actually be possible to take the spec to CR pretty quickly -- but if the group wants to put more things in conditional-4, then maybe the answer is to clear the one feature for shipping.
I can try to give writing a spec a shot, but no promises at least just yet :)
Attachment #9030840 - Attachment description: Bug 1513643 - Enable selector() function for @supports everywhere. → Bug 1513643 - Enable selector() function for @supports everywhere. r=dbaron
Pushed by email@example.com: https://hg.mozilla.org/integration/autoland/rev/468e240bf668 Enable selector() function for @supports everywhere. r=dbaron
You need to log in before you can comment on or make changes to this bug.