Re: [w3ctag/design-reviews] Other Spec Review: named-feature() function for CSS @supports (Issue #1186)

christianliebel left a comment (w3ctag/design-reviews#1186)

@dbaron Thank you for your proposal. We are concluding it as **satisfied with concerns**, with the primary concern being that you might either transfer the “Cartesian explosion” of potential combinations to the `named-feature` registry or, if it’s seldom used, end up with a potentially abandoned list that will need to be maintained indefinitely. Apart from that, we believe your proposal benefits site authors.

[Same side note as for `@supports(at-rule(…))`](https://github.com/w3ctag/design-reviews/issues/1176#issuecomment-3799821771): We believe that feature detection might theoretically allow for fingerprinting. While feature support could be derived from the user agent string, initiatives are underway to reduce its entropy, such as by freezing or restricting it. In that case, feature detection might provide an additional fingerprinting bit. However, depending on the exact feature, developers are likely already able to query support by defining a certain style and checking if it is applied properly.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1186#issuecomment-3799831049
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1186/3799831049@github.com>