You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 8, 2020. It is now read-only.
In our webapp we are using a pattern like "?9?9.?9?9.?9?9?9?" for a date field. When the Predictive Text is enabled for the Samsung device's keyboard the field behaves in a really strange way.
Chrome (v58):
You type the 1st digit and everything is ok.
You type the 2nd digit, everything remains ok.
But when you type the 3rd digit the 2nd digit is getting copied.
And then you type the 5th digit, the 3rd and the 4th are getting copied.
Firefox (v53.0.2)
The input field is totally broken.
On the other hand, when the Predictive Text is disabled (from the device's settings), everything is back to normal.
Ofc I tried to turn autocomplete off, autocapitalize=off and spellcheck to false but obviously the Samsung's Predictive text did not really care.
Has anybody experienced this behaviour before?
Any clues on what might cause it/solve it?
The text was updated successfully, but these errors were encountered:
In our webapp we are using a pattern like "?9?9.?9?9.?9?9?9?" for a date field. When the Predictive Text is enabled for the Samsung device's keyboard the field behaves in a really strange way.
Chrome (v58):
You type the 1st digit and everything is ok.
You type the 2nd digit, everything remains ok.
But when you type the 3rd digit the 2nd digit is getting copied.
And then you type the 5th digit, the 3rd and the 4th are getting copied.
Firefox (v53.0.2)
The input field is totally broken.
On the other hand, when the Predictive Text is disabled (from the device's settings), everything is back to normal.
Ofc I tried to turn autocomplete off, autocapitalize=off and spellcheck to false but obviously the Samsung's Predictive text did not really care.
Has anybody experienced this behaviour before?
Any clues on what might cause it/solve it?
The text was updated successfully, but these errors were encountered: