Bug 26519

Summary: oninput fires too often
Product: WebKit Reporter: Erik Arvidsson <arv>
Component: DOMAssignee: Nobody <webkit-unassigned>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Minor CC: ahmad.saleem792, ap, shadow2531, wenson_hsieh
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   
Attachments:
Description Flags
Detects invalid oninput events
none
Safari 15.5 matches other browsers none

Erik Arvidsson
Reported 2009-06-18 14:50:09 PDT
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.
Attachments
Detects invalid oninput events (973 bytes, text/html)
2009-06-18 14:50 PDT, Erik Arvidsson 		no flags
Details
Safari 15.5 matches other browsers (631.61 KB, image/png)
2022-05-30 15:06 PDT, Ahmad Saleem 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Erik Arvidsson
Comment 1 2009-06-18 14:50:47 PDT
Created attachment 31511 [details] Detects invalid oninput events
Michael A. Puls II
Comment 2 2009-06-20 17:35:44 PDT
(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.
Michael A. Puls II
Comment 3 2009-06-24 02:38:16 PDT
(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.
Ahmad Saleem
Comment 4 2022-05-30 15:06:48 PDT
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!
Alexey Proskuryakov
Comment 5 2022-05-31 10:31:18 PDT
Thank you for checking!
Note You need to log in before you can comment on or make changes to this bug.