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

> The problem of placing the caret in allowed positions should be instead handled by the Selection API.

We can move this part to another spec, but we still need to have this down precisely. Right now, as you know, the caret cannot be placed in certain places, so we need certain "guarantees" that the caret really can be placed in specific places with a new standard. Of course, the caret is a visual manifestation of the currently collapsed selection, so that would be an argument for moving it there, but then again, that would affect all of cE=True as well which may not be wanted. 

> If cE=typing will not create any node by default, then it is senseless for it to exist as an editing module. We should then review the whole thing and introduce cE=intent, where UAs would not have any default behavior and just intentions would be fired.

Right now that is kind of what cE=typing is. But we can change the name of it. I am not sure about the rest of this paragraph: are you saying we need to have something else in terms of functionality?

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