Re: [editing] Do everything needed to do block direction movement of the caret when in cE=Events? (#65)

> Interesting! I had a good nights sleep and now it seems somewhat less problematic.

I can't agree even after having more coffee ;). I started considering cases like floated blocks (multiple columns of text), CSS multi-column cases (which should be navigable in source order), or stuff like:

```
<p>foo<img src="x" width="50" height="50"><img src="x" width="50" height="50" style="margin-left:50px"></p>
```

which creates a gap between images that doesn't have a rect, so an algorithm based on rects would not reach it, while e.g. Chrome does.

Besides, this is still only caret movements, while the scope is much wider.

> > Or will this be problematic for browsers?
>
> That's fine with me, as long as the expectations such as #68 are clearly defined.

Great to hear this! I feel that we should focus our energy on defining such topics like #68 instead of opening the pandora's box of selection movements.

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