Re: [w3c/uievents] A way to determine what the value of an input will be if `beforeinput` is not prevented (#289)

Talking as a maintainer of editor of Firefox/Gecko, it's not impossible to implement, but it needs some big changes.

`beforeinput` event is dispatched at start of handling insertion/deletion. Therefore, the builtin editor still does not have the result. So, doing it, the builtin editor needs to handle the command/operation and dispatch `beforeinput` immediately before touching the editor value. So, the dispatcher cannot be centralized without big changes. (FYI: `getTargetRanges` for `contenteditable` causes duplicating the deletion code to compute the deleting range, therefore, the performance is not good and increased the maintenance cost.)

Cc: @johanneswilm @dandclark 

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

Message ID: <w3c/uievents/issues/289/1888338896@github.com>