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

@rniwa:

The logical meaning is basically the same: Both handle a cursor position/selection. So 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_. 

Perhaps [Microsoft Word Selection object](https://docs.microsoft.com/en-us/office/vba/api/word.selection) may give some valuable hint. It offers different types of [selections](https://docs.microsoft.com/en-us/office/vba/api/word.wdselectiontype) and [cursor movement units](https://docs.microsoft.com/en-us/office/vba/api/word.wdunits), one of them being characters.
<br/>

@tilgovi :

Looks great!

I have similar code done for my project (not on GitHub yet). It deals with `<br/>`/`\n` but doesn't deal with paragraph/block distances any further:

```js
```

-- 
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-469229513