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

> I think we've settled on a proposal here, in two parts (see [#7551 (comment)](https://github.com/w3c/csswg-drafts/issues/7551#issuecomment-1398727361)):
> 
> * No container is considered 'valid' for unknown query features (`general-enclosed`)
> * Add a comma-separated syntax for multiple queries that each find their own container. The results are combined using 'or' logic.
> 
> But I would like to get a bit more implementor confirmation here that:
> 
> * this is an acceptable approach

I think so. The consequence of that is that we no longer need the kleene logic for container queries, right?

> * we don't need a use-counter at this point

I'm about to add one for Blink:

https://chromium-review.googlesource.com/c/chromium/src/+/4654704

> /cc @lilles @anttijk @emilio

Sorry about the late response.


-- 
GitHub Notification of comment by lilles
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7551#issuecomment-1611641290 using your GitHub account


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

Received on Wednesday, 28 June 2023 15:22:03 UTC