W3C home > Mailing lists > Public > www-dom@w3.org > April to June 2009

Re: IME events

From: Daniel Danilatos <daniel@danilatos.com>
Date: Mon, 15 Jun 2009 13:52:33 +0900
Message-ID: <b2cb92d0906142152r104f51fcrb3525361c32b7c62@mail.gmail.com>
To: Olli Pettay <Olli.Pettay@helsinki.fi>
Cc: Doug Schepers <schepers@w3.org>, www-dom@w3.org, hbono@chromium.org, mnakano@mozilla-japan.org
Hi guys,
Just an update. I now have a few concrete IME related points to raise. Some
of these aren't necessarily to do with events - perhaps they belong in
another mailing list? Please let me know.

IME Events

* Firefox's compositionstart and compositionend events are great. In
particular, it is even possible to alter the dom and move the caret during
the compositionstart event, and have the IME input then take place in the
new location. I would like to see these events, or something to the same
effect, in the standard. As far as I am aware, they don't miss much that
browsers actually implement. However when things like recomposition and
document locking are fully implemented, they will also have deficiencies, so
we will need richer events.

* Consider Ojan's idea of onexeccommand - I think it has some merit (perhaps
in its original thread).


IME API

* Control the IME Candidate window (get/set position, ability to prevent it
from showing up at all, etc)

* Query the current IME state (mostly possible anyway using
compositionstart/end events)

* A way for js apps to define input context: E.g. Is this input field for a
person's name, for an address, etc? IMEs can use this information to provide
better suggestions. The TSF api allows properties to be specified on text,
perhaps some of this should be exposed in HTML? Thoughts welcome.
Received on Monday, 15 June 2009 04:53:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:14:00 GMT