- From: Emilio Cobos Álvarez via GitHub <noreply@w3.org>
- Date: Tue, 09 Sep 2025 23:48:58 +0000
- To: public-css-archive@w3.org
> By "parse time" do you mean the specified value? Yes, effectively. > The reason we simplify at computed value time here is so that the author can work with the syntax they're most comfortable with, even if they're e.g. manipulating style attributes. It's IMHO really confusing to get totally different syntax for specified and computed values without any strong reason for it, so I'd rather provide the same serialization / simplification on both ends. > There's no spec for specified value, so WebKit follows the [specified value test](https://github.com/web-platform-tests/wpt/blob/b8e8f951e5/css/css-anchor-position/position-area-parsing.html), which only swaps horizontal/x/block and vertical/y/inline keyword. I'm not opposed to simplifying `position-area` at parse time, so that the specified and computed value is the same simplified value. Right, Firefox implemented the specified value rules, and I was reviewing a patch implementing the computed value ones, and it's just weird to not perform this simplification earlier, IMHO. -- GitHub Notification of comment by emilio Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12759#issuecomment-3272659676 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 9 September 2025 23:48:58 UTC