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

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?

If the former, I think the basic idea is to give JS full control. Browsers raise events to ask JS to determine, and JS gives enough information back to browsers for it to render carets. When to raise what events, with what information, and what JS needs to give back, are what we need to discuss.

If the latter, I'm not very positive to solve it for now. It's so hard to make it interoperable at this point that we started ce=typing, hoping all editor developers move to ce=typing, and all authors move to editor frameworks based on ce=typing. If it succeeds, there should be no motivations to fix ce=true, right?

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