- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 20 Jan 2023 21:57:51 +0000
- To: public-css-archive@w3.org
The relevant change would be making `(unknown) or (width > 100px)` go from (potentially) matching to (always) skipping; the behavior for `(width > 100px) or (height > 100px)` (against an element with only `inline-size`) remains the same. I doubt there's a meaningful amount of content containing unknown CQs at this point, so no need to do a compat analysis. ------ A comma-separated list doesn't get us out of the forward-compat. You *still* have the exact same "might match different containers in old vs new browsers"; all you're doing is providing a different way to spell `or`. That said, I don't *object* to this suggested addition, especially if it gives additional power, as in Miriam's suggestion of allowing the container-name to be specified on each query. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7551#issuecomment-1399000670 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 20 January 2023 21:57:52 UTC