- From: Sam Atkins via GitHub <noreply@w3.org>
- Date: Thu, 02 Oct 2025 09:02:05 +0000
- To: public-css-archive@w3.org
AtkinsSJ has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-anchor-position-1] Use `<anchor-name>` type in `anchor-name` property grammar? == There's an `<anchor-name>` type defined [here](https://drafts.csswg.org/css-anchor-position/#typedef-anchor-name), and it's used in the [`position-anchor`](https://drafts.csswg.org/css-anchor-position/#propdef-position-anchor) grammar, but not the grammar of [`anchor-name`](https://drafts.csswg.org/css-anchor-position/#propdef-anchor-name), which uses `<dashed-ident>` directly. It looks like there are a few other places in the spec that use `<dashed-ident>` too when referring to anchor names. It seems like it would be good to consistently use the `<anchor-name>` type for those, both for clarity and to make it easier to maintain if `<anchor-name>` changes somehow in the future. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12895 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 2 October 2025 09:02:06 UTC