23830 2013-11-14 08:50:15 +0000 Move attributes of Composition interface to CompositionEvent 2014-04-08 05:12:44 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - IME API unspecified All All RESOLVED FIXED P2 major --- 1 kochi kochi masayuki mike public-webapps travil public-webapps-bugzilla oldest_to_newest 96316 0 kochi 2013-11-14 08:50:15 +0000 (Suggested by Travis at TPAC 2013) As the nature of IME composition, which may change from time to time, it makes sense to contain a 'snapshot' information of an IME composition to be delivered with CompositionEvent (e.g. compositionupdate). Rather than having 2 pieces of information separate, it will be more convenient for application developers. To do that, instead of the current form of definition: interface Composition { readonly attribute DOMString text; readonly attribute long activeSegmentStart; readonly attribute long activeSegmentEnd; sequence<unsigned long> getSegments (); }; Use: partial interface CompositionEvent { ... }; 103539 1 kochi 2014-04-08 05:12:44 +0000 This is done in the IME API annex document. https://dvcs.w3.org/hg/ime-api/raw-file/default/Annex.html#idl-def-CompositionEvent