- From: andruud via GitHub <sysbot+gh@w3.org>
- Date: Wed, 10 Apr 2024 08:10:22 +0000
- To: public-css-archive@w3.org
> > Actually, can we just make the bad situations [invalid at computed-value time](https://drafts.csswg.org/css-variables/#invalid-at-computed-value-time)?
>
> Hm, there's a thought! I... think that would be okay? It seems within the remit of that concept.
Then I think we should do that instead of "behaves as auto". Because:
- We should generally resolve things at the value stage where we have enough information to resolve that thing.
- It's consistent with the regular behavior of `anchor*()` resolving computed-value time (interleaving). For percentages-in-sizing, surviving computed-value time is business as usual. Not so for `anchor-size()`. It would only happen in this error case.
- We automatically get reasonable behavior for the property in question, also for future properties. ("Behaves as auto" does not work for `max-*`, which doesn't accept `auto`).
- The rendering pipeline after style does not need to know or care about the behavior. It makes it possible to deal with this problem more locally.
---
Regardless of the chosen approach, it would be good to clarify if the behavior should also apply to `anchor()`, or if that should stick with a `0px` fallback.
--
GitHub Notification of comment by andruud
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10005#issuecomment-2046845291 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 10 April 2024 08:10:24 UTC