RE: Added 'locale' to Text, Keyboard, and Composition Events [ISSUE-119]

I don't think it's necessary to have "input" prepended just to remind you of that all the time. I think ease of use, as Doug mentioned, is sufficient reason to leave it locale.  

Plus there's already a note in the spec to this effect:

"Note: locale does not necessarily indicate the locale of the data or the context in which it is being entered."
http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#events-TextEvent-locale


-----Original Message-----
From: Olli Pettay [mailto:Olli.Pettay@helsinki.fi] 
Sent: Tuesday, January 04, 2011 12:13 PM
To: Doug Schepers
Cc: Jacob Rossi; www-dom@w3.org
Subject: Re: Added 'locale' to Text, Keyboard, and Composition Events [ISSUE-119]

On 12/30/2010 06:10 AM, Doug Schepers wrote:
> Hi, Jacob-
>
> Jacob Rossi wrote (on 12/28/10 11:01 AM):
>>
>> On Fri, Dec 24, 2010 at 10:14 AM, Doug Schepers wrote:
>>
>>> I took the liberty of renaming 'inputLocale' to 'locale', since most 
>>> developers prefer shorter, nonCamelCased names, and it seems equally 
>>> descriptive.
>>
>> I think we had decided on inputLocale to be consistent with the 
>> naming of inputMethod. :-)
>
> We had discussed it, but I don't recall a specific resolution either 
> way. I don't consider consistency with 'inputMethod' as important as 
> ease of use, since they aren't particularly related.

I'm pretty sure we agreed to have inputLocale.
And the reason was, I think, that the 'locale' refers to the way the input was entered, not to the locale of the data in the event.

-Olli


>
> Also, 'inputMethod' is only on Text events, while 'locale' is on 
> several different interfaces.
>
> Regards-
> -Doug Schepers
> W3C Team Contact, SVG, WebApps, and Web Events WGs
>
>

Received on Tuesday, 4 January 2011 20:59:08 UTC