Debugger pauses in a strange moment inside keydown listener on composition start
Reported by
k.krz...@cksource.com,
Jun 6 2018
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36 Steps to reproduce the problem: I was debugging some collapsed/non-collapsed selection issue and prepared very simple demo of what's going on. All steps below can be easily reproduced on codepen I have prepared (https://codepen.io/f1ames/pen/oyLaqG?editors=1010). 1. Prepare 'conteneteditable=true' element with simple content. 2. Attach input events ('keydown', 'keypress', 'keyup', 'textinput', 'beforeinput', 'input', 'compositionstart', 'compositionupdate', 'compositionend') listeners to the 'document' or 'conteneteditable=true' element. 3. Each listener should have `debugger;` line inside so code execution will be paused on a first event. 4. Put selection inside 'conteneteditable=true' element. 5. Type regular character like 'a'. 6. Type Spanish accent character (with Spanish keyboard) 'ยด'. What is the expected behavior? For both 5. and 6. steps, code execution should be paused on the first event which is 'keydown' in both cases. What went wrong? For step 6. code execution is paused inside 'keydown' listener but after other event listeners were executed (even though this events happens after 'keydown') - see attached .gif file. Did this work before? N/A Chrome version: 66.0.3359.181 Channel: n/a OS Version: OS X 10.13.3 Flash Version:
,
Jun 7 2018
k.krzton@ Thanks for the issue. Able to reproduce this issue on Mac OS 10.13.3 on the reported version 66.0.3359.181 and the latest Canary 69.0.3446.0 as per the given gif file. Unable to reproduce the issue on Windows 10 and Ubuntu 14.04. This is a Non-Regression issue as this behaviour is observed from M-60 chrome builds. Hence marking this as Untriaged for further updates from Dev. Thanks..
,
Jun 11 2018
,
Sep 25
Thanks for great report! I can not reproduce it in latest Canary. If it is still an issue, feel free to file it as another issue.
,
Jan 10
Thanks, confirmed that it works on Chrome 71 (71.0.3578.98). |
||||
►
Sign in to add a comment |
||||
Comment 1 by krajshree@chromium.org
, Jun 7 2018