- From: Ben Peters <notifications@github.com>
- Date: Wed, 21 Jan 2015 09:56:24 -0800
- To: w3c/editing-explainer <editing-explainer@noreply.github.com>
Received on Wednesday, 21 January 2015 17:56:53 UTC
Copied from DOML3 Bugzilla https://www.w3.org/Bugs/Public/show_bug.cgi?id=27063 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. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/editing-explainer/issues/42
Received on Wednesday, 21 January 2015 17:56:53 UTC