[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

Gary Kacmarcik <garykac@google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |garykac@google.com

--- Comment #15 from Gary Kacmarcik <garykac@google.com> ---
Summary to see if we have a consensus here:

This bug seems to be interpreting 'beforeinput' solely in the context as a
replacement for 'keypress', but that was not the intent of 'beforeinput'. It
was introduced as a way to trap input changes (from keyboard or other input
device) before they were committed to the DOM (i.e., before the 'input' event).
It was noticed that 'beforeinput' fired whenever 'keypress' would have fired,
so 'keypress' was deemed redundant and removed (in the interest of simplifying
the number of events flying around).  Hence, 'beforeinput' is the suggested
replacement for 'keypress'.


Ojan proposed that we specify 'beforeinput' and 'input' to not fire for
execCommand so we can avoid the problems mentioned in this bug.

This seems reasonable to me.

Any further comments/suggestions?

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

Received on Tuesday, 8 April 2014 01:55:18 UTC