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

> @LeaVerou It is different from the overlapping highlight case because those are actually separate highlight objects. 

I'm not convinced this is a conceptual difference for authors vs an implementation detail. 

> Authors will expect the styles for the two highlights to be independent, and they have the option to control which styles paint on top via the `priority` property. 

This sounds like maybe the `priority` property should be specified at registration then? Just a thought.

I'm also not sure the inability to specify the priority for this edge case is that much of a problem. E.g. authors may wish to register a highlight under many different names to give their users the option of which one to use, without having to keep multiple objects in sync. I can see this being useful for syntax highlighters, e.g. Prism does provide aliases for a lot of its tokens. OTOH, I do agree that the code example presented in https://github.com/w3c/csswg-drafts/issues/5910#issuecomment-803819714 is indeed confusing.

-- 
GitHub Notification of comment by LeaVerou
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5910#issuecomment-816032758 using your GitHub account


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

Received on Thursday, 8 April 2021 18:12:04 UTC