This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 23830 - Move attributes of Composition interface to CompositionEvent
Summary: Move attributes of Composition interface to CompositionEvent
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - IME API (show other bugs)
Version: unspecified
Hardware: All All
: P2 major
Target Milestone: ---
Assignee: Takayoshi Kochi
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-14 08:50 UTC by Takayoshi Kochi
Modified: 2014-04-08 05:12 UTC (History)
4 users (show)

See Also:


Attachments

Description Takayoshi Kochi 2013-11-14 08:50:15 UTC
(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 {
...
};
Comment 1 Takayoshi Kochi 2014-04-08 05:12:44 UTC
This is done in the IME API annex document.

https://dvcs.w3.org/hg/ime-api/raw-file/default/Annex.html#idl-def-CompositionEvent