This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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.
Copied to https://github.com/w3c/editing-explainer/issues/42 Please continue the conversation there.
Bug has moved to Github issue tracking for Editing TF current work.