W3C home > Mailing lists > Public > public-css-archive@w3.org > January 2021

[csswg-drafts] [css-highlight-api] maplike vs setlike (#5910)

From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
Date: Sun, 31 Jan 2021 07:36:15 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-797645854-1612078574-sysbot+gh@w3.org>
frivoal has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-highlight-api] maplike vs setlike ==
from https://github.com/w3ctag/design-reviews/issues/584#issuecomment-767655588

> @hober and I discussed this today in our VF2F. We noticed that HighlightsRegister is a setlike, but throws when a Highlight object with an existing registered name, which indicates that perhaps maplike would have been more appropriate? It's not ideal developer experience if developers need to iterate the entire data structure before registering their object, to check if an existing one of the same name exists. Maplike would also provide an easy way to get all ranges under a given name.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5910 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 31 January 2021 07:36:16 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:26 UTC