- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 Sep 2021 16:20:28 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Invalidation of Static Ranges`, and agreed to the following: * `RESOLVED: Reference DOM's definition of invalidity for static ranges for highlight API` * `RESOLVED: Republish highlight API` <details><summary>The full IRC log of that discussion</summary> <fantasai> Topic: Invalidation of Static Ranges<br> <fantasai> github: https://github.com/w3c/csswg-drafts/issues/4597<br> <fantasai> dandclark: Discussed structures for representing highlights<br> <fantasai> dandclark: author could choose live or static ranges, with different perf considerations each<br> <fantasai> dandclark: issue was originally open to discuss, given static ranges can become stale<br> <dandclark> https://dom.spec.whatwg.org/#staticrange-valid<br> <fantasai> dandclark: what is an invalid static range that we should not try to paint?<br> <florian> q+<br> <fantasai> dandclark: Do we want to have highlight API spec point to these definitions in DOM spec, or do we want a different definition<br> <fantasai> dandclark: ...<br> <fantasai> dandclark: [reads criteria]<br> <fantasai> florian: I think it's likely a good idea to point to DOM<br> <fantasai> florian: reason this is new is that it's first time in the platform that the static range is created by user and passed to UA<br> <fantasai> florian: other uses the UA passes to user<br> <fantasai> florian: The criteria listed are reasonable, but ...<br> <fantasai> florian: but is sensitive to the length of the node<br> <Rossen_> ack florian<br> <fantasai> sanketj: Should just follow DOM definition<br> <fantasai> fantasai: what about the length?<br> <Rossen_> ack fantasai<br> <fantasai> fantasai: what is the length of a node?<br> <fantasai> sanketj: for text it's number of characters<br> <cbiesinger> is that code points? code units?<br> <fantasai> florian: so if you have an offset bigger than length of node, one behavior is to treat whole thing as invalid<br> <fantasai> florian: other behavior that we had originally was to clamp to within the length<br> <fantasai> florian: going with DOM's definition seems reasonable<br> <fantasai> Rossen_: Any objections to using DOM's definition of invalid for static ranges?<br> <fantasai> RESOLVED: Reference DOM's definition of invalidity for static ranges for highlight API<br> <sanketj> @cbiesinger, yes, code units<br> <fantasai> fantasai: Do we need to republish?<br> <fantasai> fantasai: Last publication with 2020<br> <fantasai> RESOLVED: Republish highlight API<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4597#issuecomment-915381835 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 8 September 2021 16:20:30 UTC