[Bug 28924] Is CompositionEvent supposed to have .locale?

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28924

--- Comment #2 from Takayoshi Kochi <kochi@google.com> ---
I'm not following the D3E discussion lately, but ~2years ago when I
investigated this, only IE was implementing the .locale on Composition events.
It was hard to formulate the proper value for .locale, and I gave up
including it in IME API.

I'm not sure how popular the usage is, but I guess we should avoid
abandon .locale in the spec as it is poorly spec'ed and quite hard
or sometimes meanless to expose the value on some environment.


Note: You may wonder why .locale is filled for each event, even though
.locale should rarely change between events.  I heard that the rationale
was for not leaking user's environment without user's consent - typing on
keyboard is considered an affirmative action that user let the user agent
(or the author of the content) know in which locale he/she is typing text.

Note2: the intention to include .locale in IME API was not only to
expose user's typing environment, but to *change* the locale so that
an author can *force* which language is expected to type in for
some form element etc. (i.e., .locale is writable). It might sound
useful, but quite hard to implement interoperably.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 8 July 2015 08:14:09 UTC