16972 2008-01-22 02:46:47 -0800 Wrong keyCode for Ctrl+Enter on Mac (should be 10 and not 13) 2025-09-08 18:25:09 -0700 1 1 1 Unclassified WebKit WebCore Misc. 528+ (Nightly build) Mac OS X 10.5 RESOLVED CONFIGURATION CHANGED https://bugs.webkit.org/show_bug.cgi?id=30397 InRadar, PlatformOnly P2 Normal --- 1 me webkit-unassigned ahmad.saleem792 a_protyasha ap arv karlcow oldest_to_newest 67934 0 me 2008-01-22 02:46:47 -0800 I assign keypress listener to textarea. When I press Ctrl+Enter, this listener receives event parameter with keyCode value equal to 10. But when I press just Enter, keyCode is equal to 13. It is also 13 for Ctrl+Enter in other major browsers. This is true for Safari 3.0.4 and WebKit r29711 67939 1 ap 2008-01-22 06:21:03 -0800 In my testing, Internet Explorer 7 behaves the same as Safari. It's a bug that we produce different codes for Ctrl+Enter on Windows and on Mac, but I would qualify it as a Mac-side bug. 67940 2 ap 2008-01-22 06:21:48 -0800 In other words, I think that key code should equal 10 for Ctrl+Enter, matching IE. 67941 3 me 2008-01-22 06:48:28 -0800 Sorry, I wan't attentive enough while testing IE7. I tested _keydown_ event in it, and it does produce 10 on ctrl+enter for _keypress_ event. 67943 4 ap 2008-01-22 07:13:59 -0800 I'd like to keep this open to track a bug on the Mac side - we don't have this quirk there yet, but we should. 67944 5 me 2008-01-22 07:26:08 -0800 Then please document it! : ) 75510 6 ap 2008-03-27 13:43:59 -0700 <rdar://problem/5826166> 158430 7 arv 2009-10-27 17:24:01 -0700 keypress should use the charCode (which is 13) . This seems correct on Safari Mac but wrong on Safari Windows which returns keyCode 10. What does the rdar bug say we want to do here? 158441 8 ap 2009-10-27 18:02:18 -0700 (In reply to comment #7) > keypress should use the charCode (which is 13) . You disagree with above comments - could you please explain why you find them wrong? 158447 9 arv 2009-10-27 18:30:52 -0700 (In reply to comment #8) > (In reply to comment #7) > > keypress should use the charCode (which is 13) . > > You disagree with above comments - could you please explain why you find them > wrong? I think the whole keypress issue is giving me too many sleepless nights. The reason why I found it wrong was two reasons. 1. It is valuable to be able to do String.fromCharCode(event.keyCode) in a keypress handler. 2. This is what Firefox does. I think I'm starting to lean towards not touching keypress again and tell people to only use keydown, keyup and textInput. 158449 10 ap 2009-10-27 18:59:50 -0700 > 2. This is what Firefox does. As a general rule, we do what IE does for key handling. 158451 11 arv 2009-10-27 19:38:15 -0700 (In reply to comment #10) > > 2. This is what Firefox does. > > As a general rule, we do what IE does for key handling. We should update the title to say: Wrong keyCode for Ctrl+Enter on Mac (should be 10 and not 13) 2133285 12 ahmad.saleem792 2025-07-29 19:30:10 -0700 https://w3c.github.io/uievents/tools/key-event-viewer.html <- Safari 18.6, Chrome Canary 140.0.7325.0 (Official Build) canary (arm64) and Firefox Nightly 143 (20250729210451) - all show 'Ctrl + Enter' with keyCode as 13 on macOS. @Abrar - do we need to do anything here or if I am testing this wrong? 2141775 13 a_protyasha 2025-09-08 18:24:42 -0700 (In reply to Ahmad Saleem from comment #12) > https://w3c.github.io/uievents/tools/key-event-viewer.html <- Safari 18.6, > Chrome Canary 140.0.7325.0 (Official Build) canary (arm64) and Firefox > Nightly 143 (20250729210451) - all show 'Ctrl + Enter' with keyCode as 13 on > macOS. > > @Abrar - do we need to do anything here or if I am testing this wrong? This is no longer an issue. I just tested across Safari, Chrome, and Firefox too.