Currently the oninput event fires too often. One such case is when the selection is replaced with exactly the same content. In bug 15189 it was stated that it also happens when the user presses delete and backspace and nothing is removed. I cannot reproduce that case though.
Created attachment 31511 [details] Detects invalid oninput events
(In reply to comment #1) > Created an attachment (id=31511) [review] > Detects invalid oninput events On Win32 at least, in the right-click context menu for the text field, Safari enables paste in the menu even if there isn't any clipbrd data present. This allows you to paste nothing in the textarea area, which causes 'input' to fire. The attachment detects this too, but just wanted to FYI ya.
(In reply to comment #1) > Created an attachment (id=31511) [review] > Detects invalid oninput events If you have the value "dd", highlight the second 'd' and drag it in front of the first 'd', the event shouldn't fire because the value ends up being the same. The attachment detects this too.
Created attachment 459874 [details] Safari 15.5 matches other browsers I tried to reproduce this bug in Safari 15.5 but it matches other browser as shown in the attached screenshots. I think since the output is similar to other browsers, it should be marked as "RESOLVED FIXED" or "RESOLVED INVALID". If my repo is flawed, please test and respond accordingly. Thanks!
Thank you for checking!