- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 02 Jun 2023 17:15:18 +0000
- To: public-css-archive@w3.org
Right, I think the only way in which this would really be useful is if you needed to test for a new predefined complex counter style, which you couldn't reproduce yourself with `@counter-style`. For anything you *can* reproduce with `@counter-style`, the use-case for testing for it seems very minimal at first glance. If it's not supported, you can just add support for it yourself. At *best*, maybe using this to guard an import would make sense, tho I'm pretty certain the overhead of a fresh request is gonna be larger than the extra kilobyte from inlining it instead. I'm not certain what you'd do with the query *besides* adding your own support, tho; what possible layout or styling difference would make sense to be contingent on whether a counter style was predefined or not? I could be convinced otherwise, tho. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8907#issuecomment-1574063046 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 2 June 2023 17:15:20 UTC