W3C home > Mailing lists > Public > www-dom@w3.org > October to December 2010

Re: ISSUE-155 (textinput): Consider lowercasing 'textInput' event [DOM3 Events]

From: Doug Schepers <schepers@w3.org>
Date: Wed, 20 Oct 2010 15:44:46 -0400
Message-ID: <4CBF46AE.2090200@w3.org>
To: David Flanagan <david@davidflanagan.com>
CC: www-dom@w3.org
Hi, David-

Thanks for your comments.

We discussed one of your issues, lowercasing 'textInput', at the DOM3 
Events telcon today [1], and we agree that it would be handy, and don't 
see much risk in changing it at this point.

I have changed this throughout the DOM3 Events spec, and you will see 
these changes reflected in the next editor's draft.

Please let us know whether or not you are satisfied with this resolution.

[1] http://lists.w3.org/Archives/Public/www-dom/2010OctDec/0095.html

-Doug Schepers
W3C Team Contact, SVG and WebApps WGs

Web Applications Working Group Issue Tracker wrote (on 10/20/10 12:30 PM):
> ISSUE-155 (textinput): Consider lowercasing 'text'Input' event [DOM3 Events]
> http://www.w3.org/2008/webapps/track/issues/155
> Raised by: Doug Schepers
> On product: DOM3 Events
> David Flanagan<http://lists.w3.org/Archives/Public/www-dom/2010OctDec/0065.html>:
> [[
> 0) I suspect that this has already been debated at length, but does the
> "textInput" event really have to be mixed case?  With the deprecation of
> the various DOM-prefixed event types, won't this be the only mixed-case
> event type?  Assuming that browsers expose this event with an "on"
> handler property, JavaScript programmers are going to be confused when
> typing "ontextInput" and will end up doing "onTextInput".  If a
> single-case name is good enough for genuinely hard-to-read things like
> "compositionend", it should be fine to use "textinput" for this event!
> ]]
Received on Wednesday, 20 October 2010 19:44:48 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:16 UTC