Safari: incorrect keyboard state
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 202
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
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?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the reported ProseMirror behavior involving the JavaScript selection API and virtual keyboard autocapitalize state, then read the linked WebKit bug 236937. Establish whether Safari's behavior is considered a bug or expected behavior, and record the resulting guidance for editors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100