Ok, so I’m having issues with cursor placement in Google’s search field.
E.g.: I tap the area indicated by the wobbly arrow below:
Which leads to this:
I.e. the cursor ends up in the wrong place.
It is subsequently possible to place the cursor, but it requires an extremely long finger press.
And it’s also difficult moving the cursor and pasting text into the search field.
Notes: this behaviour appears to have been caused by a change at Google’s end. That is, the change occurred without a change in iOS version or settings.
Further, the above-described behaviour occurs in Safari. In Chrome the behaviour is different - and closer to expectations. This is curious, because (as I understand it), all web browsers on iOS use Apple’s underlying web tech.
As an experiment, I tried iCab, which allows you to set the user agent identifier. When the browser identifies itself to Google Search as Safari/iOS, then it takes a very long press to get the cursor in position (approx. 1 second). If the browser identifies itself as Chrome/iOS, a short tap suffices. Different behaviours, different UA strings, same browser.
E.g.: I tap the area indicated by the wobbly arrow below:
Which leads to this:
I.e. the cursor ends up in the wrong place.
It is subsequently possible to place the cursor, but it requires an extremely long finger press.
And it’s also difficult moving the cursor and pasting text into the search field.
Notes: this behaviour appears to have been caused by a change at Google’s end. That is, the change occurred without a change in iOS version or settings.
Further, the above-described behaviour occurs in Safari. In Chrome the behaviour is different - and closer to expectations. This is curious, because (as I understand it), all web browsers on iOS use Apple’s underlying web tech.
As an experiment, I tried iCab, which allows you to set the user agent identifier. When the browser identifies itself to Google Search as Safari/iOS, then it takes a very long press to get the cursor in position (approx. 1 second). If the browser identifies itself as Chrome/iOS, a short tap suffices. Different behaviours, different UA strings, same browser.