On Thu, May 3, 2012 at 12:44 AM, Ojan Vafai wrote:
> As I've said before, I don't think command/value should be restricted to
> contentEditable beforeInput/input events. I don't see any downside to making
> command, value and text all available for all three cases. It simplifies
> things for autho
On Thu, Apr 5, 2012 at 6:19 AM, Aryeh Gregor wrote:
> On Wed, Apr 4, 2012 at 10:07 PM, Ojan Vafai wrote:
> > The original proposal to drop textInput included that beforeInput/input
> > would have a data property of the plain text being inserted. Aryeh, how
> does
> > that sound to you? Maybe the
On Wed, Apr 4, 2012 at 10:07 PM, Ojan Vafai wrote:
> The original proposal to drop textInput included that beforeInput/input
> would have a data property of the plain text being inserted. Aryeh, how does
> that sound to you? Maybe the property should be called 'text'? 'data' is
> probably too gene
BCC: www-dom
CC: public-webapps
The original proposal to drop textInput included that beforeInput/input
would have a data property of the plain text being inserted. Aryeh, how
does that sound to you? Maybe the property should be called 'text'? 'data'
is probably too generic.
On Wed, Apr 4, 2012 a
