W3C home > Mailing lists > Public > www-dom@w3.org > October to December 2013

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

From: <bugzilla@jessica.w3.org>
Date: Mon, 25 Nov 2013 10:03:05 +0000
To: www-dom@w3.org
Message-ID: <bug-23913-4009@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23913

            Bug ID: 23913
           Summary: beforeinput should be fired only when the DOM change
                    is caused by direct input by keypress or composition
           Product: WebAppsWG
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: DOM3 Events
          Assignee: travil@microsoft.com
          Reporter: masayuki@d-toybox.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, www-dom@w3.org

I strongly believe that beforeinput should be fired only when:

* the DOM change is caused by printable key press event (or Enter key etc.)
* the DOM change is caused by composition (i.e., IME)

The reason is, if beforeinput is fired at all DOM changes, the implementation
becomes very complicated and web apps must not want the events which are caused
by value change by their script.

Additionally, if we allow to dispatch beforeinput for all DOM changes, it may
cause nested events. E.g., in beforeinput event handler, script changes the
editor value again, beforeinput is fired again *before* finishes the previous
beforeinput dispatching. This is dangerous.

Similarly, editor commands shouldn't cause beforeinput event since they can be
kicked by execCommand() method.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 25 November 2013 10:03:10 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:21 UTC