This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Some attributes/methods in InputMethodContext look working well under condition that on an element with keyboard focus. So how do they do when the element loses focus? attribute Composition composition; This must be null because an IME is not composing text of course. attribute boolean enabled; As http://w3.hasb.ug/22028 says, this attribute should be considered. attribute DOMString locale; This attribute may not change by focusing. void confirmComposition (); Just do nothing like composition attribute. void setCaretRectangle (Node anchor, long x, long y, long w, long h); void setExclusionRectangle (Node anchor, long x, long y, long w, long h); These methods prepare the rectangle when an element gets focus and shows candidate window. boolean open (); It is natural that if an element gets focus, it is associated to IME. But it is little strange that to call open() method doesn't open IME immediately.
As we will drop .enabled and open() from the spec, I think most of the concerns here are already addressed. I added a note in the spec that accessing IME when the target element does not have focus is almost meaningless.