[w3c/editing] Safari: incorrect keyboard state (Issue #548)

johanneswilm created an issue (w3c/editing#548)

ProseMirror developer reports:

> Moving the selection via the JavaScript selection API or adding content next to the cursor will not update the virtual keyboard's autocapitalize state. This makes life very hard for editors that do a lot of scripting, or handle some user actions in custom ways through keydown handlers, since the user will often get an unexpected/incorrect keyboard state.
> A  big has been filed years ago:
> https://bugs.webkit.org/show_bug.cgi?id=236937

Question: Is this perceived as a bug (which will be fixed) or is this just expected/accepted behavior?

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

Message ID: <w3c/editing/issues/548@github.com>