- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Fri, 13 Dec 2019 06:49:40 +0000
- To: public-css-archive@w3.org
frivoal has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-highlight-api] invalidation of static ranges == As far as I am aware, uses of `StaticRange` prior to css-highlight-api were for ranges created by the User Agent and passed to the author. In css-highlights-api, it's the other way around, which raises (for the first time?) the question of invalidation of static ranges, as they may have become stale by the time the browser needs to use them. https://drafts.csswg.org/css-highlight-api-1/#range-invalidation defines a way to evaluate that. Is that reasonable? If not, what should we do instead? Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4597 using your GitHub account
Received on Friday, 13 December 2019 06:49:41 UTC