[csswg-drafts] [css-conditionals-5] Test for the support of a property name (#11159)

cdoublev has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-conditionals-5] Test for the support of a property name ==
This is more of a question than a proposal.

Is there any reason to not allow `@supports (property)`, `CSS.supports(property)`, `supports(property)`? 

I searched for a reason in the issues of this repo and in the www-style archives, with no success.

Today, support (of a declaration, a selector, etc) is basically defined as the ability of the UA to parse the given value and accept it in a certain context. For exemple, `<supports-decl>` represents a declaration accepted in a style rule. 

So `<supports-property>` could be a property for which the UA accepts a declaration in a style rule.

I do not know how people test the support of view transitions today, or more specifically, of cross-document view transitions, as asked in this [SO post](https://stackoverflow.com/questions/78772900/how-check-browser-support-in-css-for-view-transition-navigation-auto). Instead of checking `navigation: auto`, they could only check `navigation`. Ok, this does not save a lot of bandwidth. But it clarifies the intent. 

Actually, I asked myself this question when reading an issue about testing the support of a descriptor declaration in a nested rule. If `CSS.supports(property, value)` queries the support of `property` declared with `value` in a style rule, `CSS.supports(rule, descriptor)` and `CSS.supports(parent-rule, rule, descriptor)` could query the support of `descritor` in the given `rule` (nested in `parent-rule`) as context... which is a different topic and again, not a proposal.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11159 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 6 November 2024 13:32:01 UTC