22196 2013-05-29 08:25:52 +0000 Clarification of InputMethodContext behavior when an element losts focus. 2013-07-04 09:14:56 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - IME API unspecified PC All RESOLVED FIXED P2 normal --- 1 yoichio kochi mike public-webapps public-webapps-bugzilla oldest_to_newest 88369 0 yoichio 2013-05-29 08:25:52 +0000 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. 90345 1 kochi 2013-07-04 09:14:56 +0000 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.