Platform: iOS 8.4
Hardware: iPhone 5S
Original Bootstrap issue: https://github.com/twbs/bootstrap/issues/16988
1. Open http://jsfiddle.net/cvrebert/cjn5n4z2/show/ in iOS Safari.
2. Tap into the text input.
3. Type in a long string of text, such that the start of the text has been pushed to far to the left that it's no longer visible.
4. Attempt to move the cursor towards the start of the text by long pressing within the input and then, without taking your finger off the touchscreen, moving your finger beyond the left edge of the text input field.
The text in the input should start moving to the right, so that eventually the beginning of the text is reached.
The text in the input does not start moving to the right.
Copy of JS Fiddle testcase:
<br /><br />
<input type="text" />
/*ensure there's some empty space on both sides of the input*/
Also filed a Radar:
See also http://stackoverflow.com/questions/28544163/ios-safari-8-input-overflow-scroll
*** Bug 150260 has been marked as a duplicate of this bug. ***
How come this is not being taken seriously??
It's still a major issue.
Tested on IOS 10.3.
Tested using google.com search input field....
Please can we try and sort this asap - it is quite a glaring bug and has caused a number of users a whole lot of pain... I really don't understand why this doesn't even have an assignee despite being reported 2 years ago?!!
We hit also to this bug, is there any known workaround?
Ran into this issue today. Very inconvenient and annoying behavior. Also my QA engineer insist it has to be fixed.
It's still an issue on Safari 10 / iPhone iOS 10.
I can't understand how it's possible that this major bug is still not fixed in iOS 11.2.5 after more than two years??
Is there a known workaround?
For example: convince the iOS keyboard to show arrow keys with a CSS property?
I think Megan fixed this on trunk after adding support for autoscrolling in editable elements (see <https://trac.webkit.org/changeset/226067/webkit> and <https://trac.webkit.org/changeset/228549/webkit>).
Wenson is correct! This is resolved on trunk and should be available in the current developer seed. Please test and verify with the latest seed
*** This bug has been marked as a duplicate of bug 180789 ***