W3C home > Mailing lists > Public > www-dom@w3.org > July to September 2012

[Bug 18931] New: D3E should define when compositionupdate event is fired

From: <bugzilla@jessica.w3.org>
Date: Thu, 20 Sep 2012 09:17:36 +0000
To: www-dom@w3.org
Message-ID: <bug-18931-4009@http.www.w3.org/Bugs/Public/>

           Summary: D3E should define when compositionupdate event is
           Product: WebAppsWG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: DOM3 Events
        AssignedTo: schepers@w3.org
        ReportedBy: masayuki@d-toybox.com
         QAContact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, www-dom@w3.org

I forgot to file this issue here.

I mentioned this in the ML but nobody never replied this:

> I think D3E spec should define the timing of compositionupdate event clearly.
> On IE9, compositionupdate event is fired *after* editor content is modified actually.
> On WebKit and Gecko, it's fired *before* editor content is modified.
> That means there is a difference. That is, whether web app can access modified content by value of <input> or <textarea>, or innerHTML of editing host of a contenteditable element.
> I think that most web application developers expect IE9's behavior because compositionupdate isn't cancelable and they may want to access the modified value.
> For the compatibility between browsers, I'd like to suggest that D3E should define the timing. I recommend the IE9's behavior.

Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Thursday, 20 September 2012 09:17:37 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:19 UTC