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

> If we were talking about ce=typing, and when set from JS, IIUC, the request is browsers should never ever change the set selection, and it's up to JS (beforeinput) to make sure a text node is there. Correct?

@kojiishi Correct. I don't know what goes on in a browser, but there seem to be both problems rendering the caret in certain places (it's there, but it isn't drawn) and there are places where it simply cannot be placed (different for every browser). This list is just about to ensure that it's both possible to put the caret there (by JS) and that it's actaully drawn/rendered when it's there.

> If browsers do default cursor movements, I understand we need some logic defined. I didn't really carefully reviewed yet, but it looks like a good start. Are we also defining how to move when the caret fell into where not allowed?

Indeed. I wrote some paragraphs on that, but removed them again when it sounded like you just wanted to do movement intentions. They are still in an old commit, I can get them back. They are not perfect, but they should be better than what we have now, and they shouldn't matter much anyway if the JS can put the caret in all the above-mentioned places programmatically.

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