Re: [w3c/editing] EditContext: Who's going to handle caret navigation? (#266)

I agree with @reinmar that EditContext is not doing what is needed in terms of caret movement. But it was my understanding that one could couple EditContext with `contenteditbale=caret-only` or similar to let the browser take care of selection movement. And until such a mode exists, it should work with `contenteditable=true` where one rolls back any change that the browser may then make to the dom element (before reapplying what it really needs to do), so that one effectively created a `caret-only` mode.

Background: Creating your own selection entirely in JS for a richtext editor is difficult, yet necessary in some cases. JS editors seem to mostly work with a combination where it generally uses the browser native selection, but in some cases (such as the user selecting a column of a table), it overrides with it's own selection-mechanism.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/266#issuecomment-674131346