Windows touch keyboard ignores autocorrect="off" on input/textarea and content-editable elements
Categories
(Core :: Widget: Win32, defect)
Tracking
()
People
(Reporter: pranavmodi, Unassigned)
Details
Steps to reproduce:
Use a Windows device with a touch screen (or enable the touch keyboard via Settings > Time & Language > Typing > Touch keyboard > "Show the touch keyboard when there's no keyboard attached").
Open a page containing:
<label>autocorrect OFF:</label>
<input type="text" autocorrect="off"><br>
<label>autocorrect ON:</label>
<input type="text" autocorrect="on">
Or navigate to any page with <input autocorrect="off">.
Tap on the autocorrect="off" input field to focus it and bring up the touch keyboard.
Type a misspelled word using the touch keyboard, e.g. type "vegen" then press space.
Observe the text in the input field.
Actual results:
The text is changed to "vegan " — the touch keyboard autocorrects "vegen" to "vegan " despite autocorrect="off".
Expected results:
The text remains "vegen " — the touch keyboard should not autocorrect because autocorrect="off" is set.
| Reporter | ||
Updated•1 month ago
|
Comment 1•1 month ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::DOM: UI Events & Focus Handling' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Updated•1 month ago
|
Comment 2•1 month ago
|
||
It is possible that DOM needs to expose some more information, but somehow Windows level code needs to use that.
Comment 3•1 month ago
|
||
It's not clear whether it is even possible to pass this information to windows.
I don't see a relevant scope and for example I can't see anything field specific in the chromium code.
Pranav - does Microsoft Edge suppress the autocorrect for your test case?
Comment 4•27 days ago
|
||
This doesn't happen on my Surface tablet with the hardware keyboard removed. The software keyboard shows autocorrect options (regardless of the autocorrect setting) but doesn't autocorrect when space is pressed. I'm testing with the MDN example. I see the same behavior on Firefox and Edge..
Updated•26 days ago
|
Comment 5•21 days ago
|
||
Redirect a needinfo that is pending on an inactive user to the triage owner.
:gstoll, since the bug has recent activity, could you have a look please?
For more information, please visit BugBot documentation.
Comment 6•12 days ago
|
||
We weren't able to reproduce this, and in the absence of more info from the reporter there's nothing we can do.
Description
•