- From: Olli Pettay <Olli.Pettay@helsinki.fi>
- Date: Mon, 13 Dec 2010 17:27:47 -0800
- To: Jacob Rossi <jrossi@microsoft.com>
- CC: "www-dom@w3.org" <www-dom@w3.org>, "aharon@google.com" <aharon@google.com>
On 12/13/2010 04:44 PM, Jacob Rossi wrote: >> > 1. What about handwriting and voice? Both should be highly > >> > language-dependent, so conceptually there should be no problem with > >> > assigning to these events an input locale. Are they covered by keyboard > >> > and/or composition events? > >> > > >> > 2. An application may not need the power of working with keyboard and/or > >> > composition events, but much prefer the simplicity of text events. > For such > >> > an application, the feature would be killed (although I admit that > this is > >> > stronger language than warranted). > >> > > >> > Aharon > > Agreed, conceptually it’s not blocked from being defined for those input > methods. And so, per discussion in the telecon on Wed, it’ll be put on > KeyboardEvent, CompositionEvent, and TextEvent. However, it will be > spec’d in such a way that either “” or the correct inputLocale will be > considered passing implementations for this property since UAs may not > be able to define it accurately for all input methods. I think you mean null, not "" ;) -Olli And this way, it > enables the spec to be forward compatible should it ever become possible > for UAs to define it for more input methods not covered by Keyboard and > Composition events. > > -Jacob >
Received on Tuesday, 14 December 2010 01:28:32 UTC