- From: Gerald Monaco via GitHub <sysbot+gh@w3.org>
- Date: Thu, 03 Nov 2022 14:56:29 +0000
- To: public-css-archive@w3.org
Right -- I think the underlying concern is just that known-but-invalid values are given special treatment (compared to `unknown` values). This means that it's more likely that some use case might break if something is ever promoted from `unknown` to known-but-invalid in a future spec revision. I think the underlying suggestion is that they should fundamentally have the same behavior. One way to achieve that would be to make known-but-invalid values evaluate to `unknown`. Another way (which I think would address your concern about the auto-selection feature) would be for conditions that evaluate to `unknown` to look further up the tree for a new container until it resolves to a value or runs out of containers to test. But yeah, this probably doesn't matter too much if we don't expect any new `<size-features>` to be added in future revisions, only e.g. `<general-enclosed>` -- GitHub Notification of comment by devknoll Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7551#issuecomment-1302238294 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 3 November 2022 14:56:31 UTC