Re: [editing-explainer] What caret positions do we need to allow? (#51)

@kojiishi 

> Your item 6 of the list confused me...are we talking about within ce=typing, or are we talking about outside (ce=true) as well?

This is all about ce=typing. Whether you want to fix ce=true as well is up to you. A corresponding bug has been filed to Chrome 2 years ago: https://code.google.com/p/chromium/issues/detail?id=242110

> If the former, I think the basic idea is to give JS full control.

Yes, JS has full access. But it still needs to be able to put the caret there. This is not about where the user automatically goes. It's a list of places where it needs to be able to go if put there pro grammatically. Right now there are many places where it cannot be put at all, so we need to avoid that happens again with ce=typing. That's why it needs to be in the spec.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing-explainer/issues/51#issuecomment-106298402