126636 2014-01-08 05:59:09 -0800 Enable CSS Feature Queries by default 2014-10-04 15:01:20 -0700 1 1 1 Unclassified WebKit CSS 528+ (Nightly build) Unspecified Unspecified RESOLVED DUPLICATE 134404 P2 Normal --- 1 m.goleb+bugzilla benjamin benjamin vertigoback oldest_to_newest 965442 0 m.goleb+bugzilla 2014-01-08 05:59:09 -0800 Firefox, Chrome & Opera support CSS Feature Queries (i.e. @supports). WebKit should add support as well. 1037221 1 vertigoback 2014-09-25 06:10:13 -0700 It's 'under development' for IE: http://status.modern.ie/conditionalrules?term=@supports 1039344 2 benjamin 2014-10-03 14:19:16 -0700 Weird bug report. WebKit had support for conditional rules for a long time. It is behind the ENABLE_CSS3_CONDITIONAL_RULES flag. 1039494 3 m.goleb+bugzilla 2014-10-04 04:15:19 -0700 OK, this is a request to enable them by default. Just being implemented doesn't really help web developers. Chrome, Firefox & Opera have it enabled. It's time! 1039518 4 benjamin 2014-10-04 11:47:13 -0700 (In reply to comment #3) > OK, this is a request to enable them by default. Just being implemented doesn't really help web developers. > > Chrome, Firefox & Opera have it enabled. It's time! Hum? I assume you mean for Safari? The bug tracker for Safari is http://bugreport.apple.com 1039520 5 m.goleb+bugzilla 2014-10-04 11:54:16 -0700 So flags have no defaults? I assumed Safari is mostly compiled with default flag values. 1039521 6 m.goleb+bugzilla 2014-10-04 11:58:39 -0700 I mean, WebKit Nightly has some flags turned on and some not. And some flags must be guarding experimental features so the mere existence of an implementation behind a flag doesn't mean it's finished. 1039522 7 benjamin 2014-10-04 12:03:44 -0700 (In reply to comment #5) > So flags have no defaults? I assumed Safari is mostly compiled with default flag values. Safari is definitely not compiled with the default flags. (In reply to comment #6) > I mean, WebKit Nightly has some flags turned on and some not. And some flags must be guarding experimental features so the mere existence of an implementation behind a flag doesn't mean it's finished. WebKit Nightly allows any experimental feature if it has good tests and is relatively stable. Most experimental features are disabled in Safari (thank god :)). If you want @support to be enabled in WebKit Nightly, that's definitely possible. 1039527 8 m.goleb+bugzilla 2014-10-04 12:21:44 -0700 Thanks for the clarification. :) Should I open a separate bug for that? 1039529 9 benjamin 2014-10-04 12:32:18 -0700 (In reply to comment #8) > Thanks for the clarification. :) Should I open a separate bug for that? Let's just repurpose this one. 1039542 10 benjamin 2014-10-04 15:01:20 -0700 I was gonna enable the flag but I see it is already on. Bear enabled it back in July: https://bugs.webkit.org/show_bug.cgi?id=134404 For Safari itself, you can do two things: 1) File a bug report asking it to be enabled in the next version: http://bugreport.apple.com 2) Write test cases for WebKit. (1) will basically be like a vote. It is saying that at least one user wants this feature. If there are already existing reports, your "vote" will add up to the original radar by marking it as duplicate. (2) will help convincing the WebKit community that the feature is ready for prime time. When a feature has outstanding test coverage and there is a strong confidence that it follows the specification, its flag is removed and the feature can no longer be disabled. WebKit has much stronger policies than Mozilla and Google in that respect, we want a lot of good tests. *** This bug has been marked as a duplicate of bug 134404 ***