1Password iOS not correctly recognising fields
I have a weird problem and hope to get some help in determining if this is a bug in 1P or of the website.
When visiting the following url: https://mijn.afaspersonal.nl/app/inloggen and trying to log in with valid credentials (using 1P autofill obviously) works fine.
However, when visiting this url: https://mijn.afaspersonal.nl/#/app/inloggen everything looks the same, but 1P does not seem to be able to find the fields properly, so autofill is not working.
Sometimes I get redirected to the hash-containing url by the application, so it is hard to figure out when the problem will occur.
Some help/thoughts appreciated.
1Password Version: 7.2.1
Extension Version: Not Provided
OS Version: iOS 12.0.1
Sync Type: 1P Families
Comments
-
Greetings @Kobes,
The URL with the # (https://mijn.afaspersonal.nl/#/app/inloggen) has the sign-in form contained in an iframe while the other one doesn't. iframes have been a weakness of the 1Password for iOS Safari extension unlike on Mac and Windows. Thankfully iOS 12's AutoFill feature and 1Password's ability to use it do offer a way around this limitation. You can learn more about AutoFill on our support page Use 1Password to fill and save on your iPhone and iPad. Previously that page would have shown how to set up the 1Password for iOS Safari extension, now it shows how to enable AutoFill. Do you find you can fill when you use it?
0 -
Ah, I did inspect the dom already before posting this issue, but not close enough apparently. I missed the iframe (was focussing mainly on the field identifiers to work out if that made a difference).
I guess it does indeed work with the new safari auto fill. However, I had also been trying using the browser shipping inside the 1P iOS app. That did not help either, but this could very well be related to the fact that any web view in iOS is actually just a re-wrapped safari of course.
0 -
Hi @Kobes,
The built-in browser (previously known as 1Browser) is a wrapper for one of the iOS web views (there's a couple, I forget which we use) and so it does have the same limitation as our Safari extension as as it's essentially the same filling code being used here as well.
0
