218507 2020-11-03 04:31:02 -0800 Up and down arrow keys in <input> have a different behavior when inside a shadow root 2020-11-07 20:41:20 -0800 1 1 1 Unclassified WebKit Forms Safari 14 Mac macOS 10.15 NEW https://bugs.webkit.org/show_bug.cgi?id=172567 InRadar P2 Normal --- 148695 1 cory webkit-unassigned akeerthi cdumez darin rniwa smoley webkit-bug-importer wenson_hsieh oldest_to_newest 1703940 0 cory 2020-11-03 04:31:02 -0800 When an <input> is present inside a shadow root, pressing the up/down arrows no longer moves the cursor to the start/end of the field. The following fiddle demonstrates a standard input with the correct behavior and an input within a shadow root with differing behavior. Fiddle: https://jsfiddle.net/me9yatxz/1/ 1704156 1 darin 2020-11-03 12:58:38 -0800 Does anyone know if this is a recent change or a long-standing issue? 1704489 2 smoley 2020-11-04 10:39:56 -0800 This also reproduces on Safari 13.1.2. 1704490 3 webkit-bug-importer 2020-11-04 10:40:17 -0800 <rdar://problem/71042487> 1704695 4 darin 2020-11-04 18:21:54 -0800 Seems like this bug is in Safari, not WebKit. 1704705 5 darin 2020-11-04 18:42:11 -0800 Safari uses JavaScript to get metadata about the text field, and when it can’t because the field is in a shadow tree, its code misfires and blocks the up and down arrows. The misbehaving code is in Safari for handling autocompletion lists. The smaller fix is to make it just not screw up and confuse itself when the text field is in a shadow tree. The bigger fix would be to make autocompletion work with those fields too. 1704900 6 darin 2020-11-05 09:28:59 -0800 The test case works as expected in MiniBrowser, and likely in other WebKit-based browsers. There is a slim chance that some kind of change in WebKit could solve the problem, since it’s indirectly due to difficulty getting data about the text field from the Safari code.