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 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
- we don't need a use-counter at this point

/cc @lilles @anttijk @emilio 

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


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

Received on Thursday, 26 January 2023 18:51:52 UTC