events when a dead key sequence is aborted by unsupported base char

Hi,
referring to 6.2.3 second example: this is not what browsers actually do  
per my testing.

^ and q will cause two different keypress (and/or textInput) events, one  
for the circumflex and one for the base character. The keydown for the  
incompatible base character triggers two keypress events, first the one  
"inherited" from the dead key, then the base character.


-- 
Hallvord R. M. Steen, Core Tester, Opera Software
http://www.opera.com http://my.opera.com/hallvors/