[Bug 24044] How do browsers decide combining character from non-combining character at computing .key value of dead key?

[email protected]
Newsgroups gmane.comp.web.dom.general
Message-ID <[email protected]/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24044

Travis Leithead [MSFT] <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #4 from Travis Leithead [MSFT] <[email protected]> ---
First attempt at a fix in changelist:
https://dvcs.w3.org/hg/dom3events/rev/662bf4d9897a

Re-worked some sections of the prose to more accurately reflect what changes we
are making regarding dead keys and the firing of composition events (we had
already decided on this, but the spec text was inconsistent, and so I fixed
those cases when scanning for occurrences of "dead keys".

I also added "Dead Key" to the key tables in the key values spec in the
IME/Composition section (seemed most appropriate).

Please review the example event sequences and make sure it's correct and that I
didn't miss anything.

Thanks!

-- 
You are receiving this mail because:
You are on the CC list for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.