Re: [w3c/editing] Inconsistent `KeyboardEvent.shiftKey` behavior for virtual keyboard autocapitalization (Issue #542)

johanneswilm left a comment (w3c/editing#542)

Call 2026-07-09:

> Michael Aufreiter described the issue as using modifier keys, such as 
Shift+Enter, on mobile virtual keyboards. On iOS, auto-capitalization 
can cause the Shift modifier to appear even when the user did not 
explicitly press it, while Android behaves differently. As a result, 
editors cannot reliably use modifier keys on mobile.
Wenson Hsieh explained that, on iOS, auto-capitalization is intended to 
be handled transparently by the system, and modifier key combinations 
are not part of the platform's interaction model. He suggested that the 
VirtualKeyboard API may be a better way to detect when a software 
keyboard is in use.
Michael agreed that editor developers should likely avoid relying on 
modifier keys on mobile and instead use platform-appropriate UI or the 
VirtualKeyboard API where available.
Dan Clark suggested documenting this behavior as non-normative guidance 
for developers.
Olli Pettay noted that the UI Events specification is currently being 
split into smaller specifications, but agreed that an issue could still 
be filed there.
Action: Michael will file an issue in the UI Events repository proposing 
guidance that modifier keys should not be relied upon on mobile 
platforms.


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

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