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
Happen to be working on some legacy code and noticed that on a site with v1.1b of the plugin the autotabbing works on iOS Safari 8 and 9 but not on 6, there is a slight issue in that the page jumps slightly after each autotab action though.
After updating the plugin to v1.9.2 the autotab doesn't work on iOS Safari but I noticed while autotabbing next doesn't work, pressing backspace does focus you back to the previous input, which looks due to the autotab-previous code not having the iOS check.
So I've set the property iOS to false in the settings object, and now autotabbing works as expected on iPhone5/6/6+ iPad2/4 running iOS 8 or 9, iOS 6 doesn't work as expected, don't have iOS7 to test.
Also in other testing the plugin version 1.9.2 does not work on Chrome v36 and v39 but as these are old I wasn't too worried but was still curious to understand why.
Thanks!
The text was updated successfully, but these errors were encountered:
Those are interesting points. When I get a chance to work on this again (it's been way too long), I'll be sure to give iOS extra attention in my testing.
Happen to be working on some legacy code and noticed that on a site with v1.1b of the plugin the autotabbing works on iOS Safari 8 and 9 but not on 6, there is a slight issue in that the page jumps slightly after each autotab action though.
After updating the plugin to v1.9.2 the autotab doesn't work on iOS Safari but I noticed while autotabbing next doesn't work, pressing backspace does focus you back to the previous input, which looks due to the autotab-previous code not having the iOS check.
So I've set the property iOS to false in the settings object, and now autotabbing works as expected on iPhone5/6/6+ iPad2/4 running iOS 8 or 9, iOS 6 doesn't work as expected, don't have iOS7 to test.
Also in other testing the plugin version 1.9.2 does not work on Chrome v36 and v39 but as these are old I wasn't too worried but was still curious to understand why.
Thanks!
The text was updated successfully, but these errors were encountered: