This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 27063 - Add "intention" integration point to 'beforeinput' event's interface
Summary: Add "intention" integration point to 'beforeinput' event's interface
Status: RESOLVED MOVED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - DOM3 Events (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Travis Leithead [MSFT]
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-15 18:37 UTC by Travis Leithead [MSFT]
Modified: 2015-01-21 20:38 UTC (History)
3 users (show)

See Also:


Attachments

Description Travis Leithead [MSFT] 2014-10-15 18:37:24 UTC
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.
Comment 1 Ben Peters 2015-01-21 18:01:10 UTC
Copied to https://github.com/w3c/editing-explainer/issues/42

Please continue the conversation there.
Comment 2 Travis Leithead [MSFT] 2015-01-21 20:38:04 UTC
Bug has moved to Github issue tracking for Editing TF current work.