[Bug 23258] New: Consider composition event order relative to IME API info when choosing to update DOM after compositionupdate...

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23258

            Bug ID: 23258
           Summary: Consider composition event order relative to IME API
                    info when choosing to update DOM after
                    compositionupdate...
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: DOM3 Events
          Assignee: travil@microsoft.com
          Reporter: travil@microsoft.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, www-dom@w3.org

I previously thought it would be good to change the compositionupdate event to
fire before the value of the input element is changed in the DOM.

However, in an internal review around the IME API, it seems we may want to
reconsider this.

The scenario is that the IME API introduces additional information that can be
observed during an IME composition. This information includes (but is not
limited to) the character indexes where the active composition is taking place,
the current candidate window placement or exclusion rectangle, etc. It is
expected that web developers will interact with the IME API during a
composition, primarily those triggered by compositionupdate events. If the DOM
is not yet updated until after compositionupdate fires, then usage of the IME
API (relative to the content in the DOM) will be slightly out-of-date (to be
refreshed in the DOM immediately after compositionupdate is finished
dispatching.

A suggestion in the current IME API is to possibly include some of the
state-full information on the composition events themselves, but we should
probably have a discussion on this.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Monday, 16 September 2013 21:42:48 UTC