- From: Oriol Brufau via GitHub <sysbot+gh@w3.org>
- Date: Wed, 19 Oct 2022 22:04:35 +0000
- To: public-css-archive@w3.org
Maybe "should" rather than "must"? Logical and physical properties are paired and each pair shares a computed value. So if they have different grammars, then a property may end up with a computed value that can't be represented by its grammar. I guess it would be possible to serialize it as an empty string, but this would break libraries like html2pdf that iterate all computed values and expect them to work. I think it's a requirement that we should keep to have a sane behavior. And OK some details can be different like physical properties accepting quirky lengths unlike logical properties, but this is just some aliasing at parse time. Or it might also be fine if the same computed value was represented in different ways by the logical and physical properties. But that's not the case for `anchor()`. -- GitHub Notification of comment by Loirooriol Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7847#issuecomment-1284621106 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 19 October 2022 22:04:37 UTC