[Bug 23913] beforeinput should be fired only when the DOM change is caused by direct input by keypress or composition

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23913

--- Comment #13 from Masayuki Nakano <masayuki@d-toybox.com> ---
(In reply to Ojan Vafai from comment #12)
> How about we change beforeInput and input to not fire for execCommand? They
> would still fire for user-initiated cut, paste, etc.

I don't think it makes sense to prevent firing input event in such cases
because web apps must expect input event is fired for every modifying the
content. If not, it's not useful for implementing autocomplete/suggest list.

beforeinput is designed for an alternative event of keypress event. Therefore,
it's cancellable and it causes different issues from input event.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 10 December 2013 07:52:30 UTC