Re: [csswg-drafts] [cssom-view] Remove `caret range` concept from `CaretPosition` interface (#10230)

yeah, the spec doesn't really make sense. Gecko does internally create a temporary Range just to call getBoundingClientRect and after that the Range is released, so it won't observe mutations to DOM.

I think this stuff comes initially from https://github.com/w3c/csswg-drafts/commit/532723f180343305397c6ede736854cb90ea6e8e

I don't see that being discussed in
https://www.w3.org/Bugs/Public/buglist.cgi?product=CSS&component=CSSOM%20View&resolution=---
So perhaps it came from the mailing list.

Here https://lists.w3.org/Archives/Public/www-style/2009Nov/0244.html
I didn't try to find the relevant TPAC meeting minutes.

Oh, and looks like I complained about the range already 13 years ago :) https://lists.w3.org/Archives/Public/www-style/2011May/0051.html

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


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

Received on Monday, 29 April 2024 20:07:46 UTC