27063 2014-10-15 18:37:24 +0000 Add "intention" integration point to 'beforeinput' event's interface 2015-01-21 20:38:04 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - DOM3 Events unspecified PC Windows NT RESOLVED MOVED P2 normal --- 1 travil travil benjamp mike www-dom public-webapps-bugzilla oldest_to_newest 113235 0 travil 2014-10-15 18:37:24 +0000 In http://w3c.github.io/editing-explainer/commands-explainer.html, there is a desire to unify the various editing/input scenarios behind intentions. beforeinput is one on their radar (along with beforeselectionchange (Selection API spec), and clipboard events). IndieUI is also invested here. The ask is to give beforeinput a 'intention' (DOMString) property. They also want to unify on a way to present the 'data' (currently included in InputEvent as 'data' :-). In addition, there are various ideas on how to further express this. One approach is to provide a Range (the about-to-be-affected content), and the expected thing that will replace it. It is unclear whether we would spec this, or they would spec it. If we do it, we should follow the intention explainer. 117398 1 benjamp 2015-01-21 18:01:10 +0000 Copied to https://github.com/w3c/editing-explainer/issues/42 Please continue the conversation there. 117406 2 travil 2015-01-21 20:38:04 +0000 Bug has moved to Github issue tracking for Editing TF current work.