- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Tue, 08 Jun 2021 00:56:47 +0000
- To: public-css-archive@w3.org
Well, both my example fallbacks are based on existing CSS mechanisms. One is used for parse-time issues like invalid syntax, while the other is used for computed-value-time issues like invalid custom properties. Looking back through the transcript, it seems like we plan resolve these units at computed value time, which means we're in custom-property (invalid-at-computed-value-time/IACVT) territory. So, having suggested it, I now think we _can't_ use the parse-time fallback, even if we wanted to? So that complicates things a bit more. I think ideally we might want: - A decent default that ensures we always get _some_ value, even if it's not ideal in all cases (are there better options than viewport?) - Some way to provide an IACVT fallback, to override that default -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5888#issuecomment-856359244 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 8 June 2021 00:57:43 UTC