Re: [selection-api] caret-based selection movement (#27)

> But it would also be problematic if it would be completely impossible to move the caret either directly before or after it (at least programmatically).

The way I see it we are just trying to sort out default behaviors (what the UA does if the user's Intent is allowed to continue without intervention by the editor). I think that editor dev would be able to programmatically set the caret on either side of the display:none element if necessary.

>  Maybe we should start out by looking at possible use cases for this?

Sure! May I turn this around on you? What use case is there where an invisible display:none element should be treated as one character? 

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/selection-api/issues/27#issuecomment-65951995