Re: [w3c/selection-api] Add Selection/Range methods based on anchestor element (#102)

> The logical meaning is basically the same: Both handle a cursor position/selection. Thus, I'd suggest to keep it with the Selection API. The sole difference is: The current logic is based on nodes, the suggested logic is based on characters.

No, my point was that this is an API that is useful without the pretense of a selection. It's useful to be able to say, point to the character X from the beginning of an element E. So this should really be a DOM API.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/selection-api/issues/102#issuecomment-469446981