193255 2019-01-08 14:30:23 -0800 [iOS] Command + . key events to non-editable elements have incorrect key details 2019-01-09 15:02:08 -0800 1 1 1 Unclassified WebKit WebCore Misc. WebKit Local Build iPhone / iPad iOS 12 RESOLVED DUPLICATE 192824 https://bugs.webkit.org/show_bug.cgi?id=193258 https://unixpapa.com/js/testkey.html InRadar, PlatformOnly P2 Normal --- 190571 1 dbates webkit-unassigned webkit-bug-importer oldest_to_newest 1492763 0 dbates 2019-01-08 14:30:23 -0800 Seen on iOS using a hardware keyboard. Steps to reproduce: 1. Visit <https://unixpapa.com/js/testkey.html>. 2. Ensure Modifiers and DOM 3 attribute values are enabled. 3. Press Command + . on the keyboard. Then the properties keyCode, which, charCode and key have values 85, 85, 85, and UIKeyInputEscape, respectively. But the values of these properties should be 27, 27, 0, and Escape, respectively to match Mac. 1492817 1 webkit-bug-importer 2019-01-08 16:49:28 -0800 <rdar://problem/47133149> 1493122 2 dbates 2019-01-09 14:58:23 -0800 (In reply to Daniel Bates from comment #0) > Seen on iOS using a hardware keyboard. > > Steps to reproduce: > > 1. Visit <https://unixpapa.com/js/testkey.html>. > 2. Ensure Modifiers and DOM 3 attribute values are enabled. > 3. Press Command + . on the keyboard. > > Then the properties keyCode, which, charCode and key have values 85, 85, 85, > and UIKeyInputEscape, respectively. But the values of these properties > should be 27, 27, 0, and Escape, respectively to match Mac. Actually, on Mac we do not convert Command + . to Escape. 1493124 3 dbates 2019-01-09 14:59:39 -0800 (In reply to Daniel Bates from comment #0) > Seen on iOS using a hardware keyboard. > > Steps to reproduce: > > 1. Visit <https://unixpapa.com/js/testkey.html>. > 2. Ensure Modifiers and DOM 3 attribute values are enabled. > 3. Press Command + . on the keyboard. > > Then the properties keyCode, which, charCode and key have values 85, 85, 85, > and UIKeyInputEscape, respectively. But the values of these properties > should be 27, 27, 0, and Escape, respectively to match Mac. The expected output should be: keydown keyCode=91 ([) which=91 ([) charCode=0 shiftKey=false ctrlKey=false altKey=false metaKey=true key=Meta char=undefined location=1 repeat=false keydown keyCode=190 which=190 charCode=0 shiftKey=false ctrlKey=false altKey=false metaKey=true key=. char=undefined location=0 repeat=false keyup keyCode=91 ([) which=91 ([) charCode=0 shiftKey=false ctrlKey=false altKey=false metaKey=false key=Meta char=undefined location=1 repeat=false 1493127 4 dbates 2019-01-09 15:02:08 -0800 This will be fixed in as a side effect of fixing bug #192824 and using the same code path for both hardware key presses in non-editable elements as we do for hardware key presses in editable elements. *** This bug has been marked as a duplicate of bug 192824 ***