193040 2018-12-26 17:31:50 -0800 HTMLInputElement.select() doesn't work in iOS Safari 2019-02-02 18:34:11 -0800 1 1 1 Unclassified WebKit Forms Safari 12 iPhone / iPad iOS 12 RESOLVED DUPLICATE 193758 InRadar P2 Normal --- 1 corsar89 webkit-unassigned bfulgham cdumez corsar89 dbates rniwa webkit-bug-importer wenson_hsieh oldest_to_newest 1490853 0 corsar89 2018-12-26 17:31:50 -0800 HTMLInputElement.select() doesn't work in iOS Safari. While in desktop Safari it works fine. For now, it's only modern browser without the support of `.select()` method. `.setSelectionRange()` or `selectionStart` with `selectionEnd` should be used as workaround. 1490907 1 webkit-bug-importer 2018-12-27 11:28:59 -0800 <rdar://problem/46962874> 1491262 2 cdumez 2019-01-02 14:29:09 -0800 I can see there is not IOS specific code in our select implementation: void HTMLTextFormControlElement::select(SelectionRevealMode revealMode, const AXTextStateChangeIntent& intent) { // FIXME: We should abstract the selection behavior into an EditingBehavior function instead // of hardcoding the behavior using a macro define. #if PLATFORM(IOS_FAMILY) // We don't want to select all the text on iOS. Instead use the standard textfield behavior of going to the end of the line. setSelectionRange(std::numeric_limits<int>::max(), std::numeric_limits<int>::max(), SelectionHasForwardDirection, revealMode, intent); #else setSelectionRange(0, std::numeric_limits<int>::max(), SelectionHasNoDirection, revealMode, intent); #endif } Clearly, we have an implementation of HTMLInputElement.select() on all platforms. However, the iOS implementation is a bit different for some reason. 1501561 3 rniwa 2019-02-02 18:30:55 -0800 Wenson, didn't we just fix this behavior recently? 1501562 4 wenson_hsieh 2019-02-02 18:34:11 -0800 (In reply to Ryosuke Niwa from comment #3) > Wenson, didn't we just fix this behavior recently? Yep, in https://bugs.webkit.org/show_bug.cgi?id=193758! (Sorry for the forward dupe — I probably should've found this existing bug before filing a new one). *** This bug has been marked as a duplicate of bug 193758 ***