225723 2021-05-12 16:38:09 -0700 Restoring selection ranges causes text input to ignore keypresses 2023-02-26 11:22:31 -0800 1 1 1 Unclassified WebKit DOM Safari 14 Unspecified Unspecified NEW InRadar P2 Normal --- 1 nlawson webkit-unassigned ahmad.saleem792 ap bfulgham rniwa webkit-bug-importer wenson_hsieh oldest_to_newest 1759458 0 428433 nlawson 2021-05-12 16:38:09 -0700 Created attachment 428433 Minimal repro Steps to reproduce: 1. Go to https://bl.ocks.org/nolanlawson/raw/c7d8ed3d43dbb4a018fb392467fae365/ 2. Click the text input with a mouse 3. Try to type letters on the keyboard Expected: The input receives the keypresses and show them. Actual: The input remains focused, but it isn't able to receive keypresses, and the cursor no longer blinks. Details: This issue is reproducible in Safari and Chrome, but not Firefox. It's also reproducible in Safari Technology Preview 124 (Safari 14.2, WebKit 15612.1.11.10). 1759459 1 nlawson 2021-05-12 16:39:04 -0700 For the record, I filed the same bug on Chromium: https://bugs.chromium.org/p/chromium/issues/detail?id=1208631 1759927 2 rniwa 2021-05-13 17:33:21 -0700 This is sort of expected since in WebKit, all typing goes to where the selection is, and Range in this case isn't representing any position inside the input element. We should probably be clearing the focus in this case, however. 1760110 3 nlawson 2021-05-14 09:37:20 -0700 Thanks for the feedback. Since this didn't repro in Firefox (or IE11 incidentally), I assumed it was a WebKit/Blink bug. My assumption as a web developer is that clearing a Selection of its Ranges and then adding those same Ranges back would be a non-destructive action. If that's not the case, then is there a way to formulate this as a bug to file on Firefox? Something like "When `selection.removeAllRanges()` is called, focus should be cleared"? It's not clear to me from the spec how to phrase this: https://w3c.github.io/selection-api/#dom-selection-removeallranges 1761769 4 webkit-bug-importer 2021-05-19 16:39:18 -0700 <rdar://problem/78231107> 1890325 5 ahmad.saleem792 2022-08-10 10:19:11 -0700 I am able to reproduce this bug in Safari 15.6 / TP 150 on macOS 12.5 and I am unable to type in input field. It is same with Chrome Canary 106 while Firefox Nightly 105 allows to type in the field. Just wanted to update status. Thanks! 1936867 6 ahmad.saleem792 2023-02-26 11:22:31 -0800 I am able to reproduce this bug in WebKit ToT (260854@main) with Live Range Selection API enabled as well. Just wanted to confirm that it still exist. 428433 2021-05-12 16:38:09 -0700 2021-05-12 16:38:09 -0700 Minimal repro index.html text/html 591 nlawson PCFET0NUWVBFIGh0bWw+CjxodG1sIGxhbmc9ImVuIj4KPGhlYWQ+CiAgPG1ldGEgY2hhcnNldD0i VVRGLTgiPgogIDx0aXRsZT5SYW5nZXMgaXNzdWUgcmVwcm88L3RpdGxlPgo8L2hlYWQ+Cjxib2R5 Pgo8aDE+UmFuZ2VzIGlzc3VlIHJlcHJvPC9oMT4KPGxhYmVsPgogIENsaWNrIGFuZCB0aGVuIHR5 cGUgaGVyZToKICA8aW5wdXQgdHlwZT0idGV4dCI+CjwvbGFiZWw+CjxzY3JpcHQ+CiAgZG9jdW1l bnQucXVlcnlTZWxlY3RvcignaW5wdXQnKS5hZGRFdmVudExpc3RlbmVyKCdjbGljaycsIGZ1bmN0 aW9uICgpIHsKICAgIHZhciBzZWxlY3Rpb24gPSBnZXRTZWxlY3Rpb24oKQogICAgdmFyIHJhbmdl cyA9IFtdCiAgICBmb3IgKHZhciBpID0gMDsgaSA8IHNlbGVjdGlvbi5yYW5nZUNvdW50OyBpKysp IHsKICAgICAgcmFuZ2VzLnB1c2goc2VsZWN0aW9uLmdldFJhbmdlQXQoaSkpCiAgICB9CiAgICBz ZWxlY3Rpb24ucmVtb3ZlQWxsUmFuZ2VzKCkKICAgIHJhbmdlcy5mb3JFYWNoKGZ1bmN0aW9uIChy YW5nZSkgewogICAgICBzZWxlY3Rpb24uYWRkUmFuZ2UocmFuZ2UpCiAgICB9KQogIH0pCjwvc2Ny aXB0Pgo8L2JvZHk+CjwvaHRtbD4K