Bug 217695 - `inputType` of `beforeinput` and `input` events fired when choosing a correct spell of the spellchecker is wrong
Summary: `inputType` of `beforeinput` and `input` events fired when choosing a correct...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: HTML Editing (show other bugs)
Version: Safari 14
Hardware: Mac macOS 10.15
: P2 Normal
Assignee: Nobody
URL:
Keywords: BrowserCompat, InRadar
Depends on:
Blocks:
 
Reported: 2020-10-13 21:51 PDT by Masayuki Nakano
Modified: 2024-05-07 00:31 PDT (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Masayuki Nakano 2020-10-13 21:51:55 PDT 
1. Go to https://d-toybox.com/studio/lib/input_event_viewer.html
2. Choose "<div contenteditable>"
3. Type "Speeed" into the editor below "Test editor beahvior:"
4. Then, the word should be underlined by the spellchecker.
5. Right click on the word and choose "Speed".

Then, a pair of `beforeinput` and `input` events is fired as expected, but `inputType` is `"insertText"`, although it should be `"insertReplacementText"`.
https://www.w3.org/TR/input-events-2/#interface-InputEvent-Attributes

Maybe related to bug 177657.
Comment 1 Radar WebKit Bug Importer 2020-10-14 12:50:46 PDT 
<rdar://problem/70304509>
Comment 2 sideshowbarker 2024-05-05 22:15:50 PDT 
Nakano-san, Do you know if we have any relevant WPT tests for this? And is the Chrome behavior for this case spec-conforming?
Comment 3 Masayuki Nakano 2024-05-07 00:31:30 PDT 
(In reply to sideshowbarker from comment #2)
> Nakano-san, Do you know if we have any relevant WPT tests for this? And is
> the Chrome behavior for this case spec-conforming?

Unfortunately, there is no WPT for this because there is no way to work with spellchecker UI of the browsers.