[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 #16 from Masayuki Nakano <masayuki@d-toybox.com> ---
I think that "input" should be fired even when beforeinput is not fired because
input event is always fired on current browser and it can be dispatched when it
becomes safe.

"beforeinput"'s problem is caused by that it's a cancelable event.

If "beforeinput" should always be fired before "input", I'd like to suggest
that "beforeinput" MAY be non-cencelable if it cannot be dispatched before
actual DOM change due to unsafe caused by something. This might make web apps
implementation simpler.

Please note that when "beforeinput" isn't cancelable due to unsafe, the change
is caused by web apps, not normal text input by users (caused by key, IME and
paste).

It might be unsafe when editor is changed by execCommand, setting .value, using
innerHTML or something to contenteditable editor.

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

Received on Wednesday, 16 April 2014 01:16:24 UTC