Re: [csswg-drafts] [css-contain-3] Inconsistent handling of known and unknown features jeopardizes backward compatibility (#7551)

I think it's inconsistent, though, that if you use `(width > 50px) or (height > 50px)`, the query container will be the nearest that supports queries for *both* width and height. But if you use `(width > 50px) or invalid()`, the container will be the nearest ancestor that supports queries for `width`, ignoring `invalid()`.

Or well, that's the interpretation that all the implementations did, but the [spec](https://drafts.csswg.org/css-contain-3/#container-rule) says

> the [query container](https://drafts.csswg.org/css-contain-3/#query-container) to be queried is selected from among the element’s ancestor query containers that are established as a valid query container for all the [container features](https://drafts.csswg.org/css-contain-3/#container-feature) in the [`<container-query>`](https://drafts.csswg.org/css-contain-3/#typedef-container-query)

It's not completely clear, but I would rather consider that no ancestor can be a valid container for unrecognized features.

-- 
GitHub Notification of comment by Loirooriol
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7551#issuecomment-1397791032 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 00:44:50 UTC