Re: [csswg-drafts] [css-anchor-1] Ability for a single element to have multiple anchor names (#8837)

The CSS Working Group just discussed `[css-anchor-1] Ability for a single element to have multiple anchor names`, and agreed to the following:

* `RESOLVED: make the anchor-name property a comma-separated list of idents`

<details><summary>The full IRC log of that discussion</summary>
&lt;dbaron> TabAtkins: right now spec is written so an element can only have anchor name.  Might want to allow something to be multiply named for different contexts.  You *can* work around it, but it can be annoying.  No reason to not allow multiple anchor names, not difficult in any way.  So want to make anchor-name property a comma-separated list of names.<br>
&lt;dbaron> TabAtkins: fantasai said comma-separated<br>
&lt;dbaron> fantasai: yes, we should try to be consistent<br>
&lt;dbaron> RESOLVED: make the anchor-name property a comma-separated list of idents<br>
&lt;dbaron> TabAtkins: there's a sub-discussion:  at the moment, with only one possible anchor name, it's unambiguous dealing with implicit anchors.  If you give something an anchor name.... er, wait.  There's something at the end of Romain's issue.  It's either invalid or we'll deal with it later.<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8837#issuecomment-1690145010 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 23 August 2023 15:11:58 UTC