Safari extension appearance and behavior after ios 9

Larre

After installing ios 9 and 1Password 6 on my iPad, the Safari extension doesn't seem to work like it did prior to the updates. The new version has such a small input field for the master password that all you see in the field is "mast...". Then, after entering the password, you have to manually move the keyboard out of the way before you can press the lock button to unlock the extension--I believe that previously, you just pressed the lock and the keyboard moved and the extension unlocked. And while the extension is unlocking, the "decrypting" status word is kinda superimposed on the rest of the graphics there. Not pretty. Is there something that I need to do to restore the previous behavior?

---

1Password Version: 6.0.1
Extension Version: 6.0.1
OS Version: ios 9
Sync Type: Not Provided

Ben

Hi @Larre,

Could you please let us know if you have any of the accessibility settings (under Settings > Accessibility) turned on? Particularly Larger Text, Bold Text and Zoom?

Thanks.

Ben

Larre

Hi Ben -
No, all of those features are OFF.
Larre

Unknown

This content has been removed.

Jacob

@Larre @Bernfrin What devices are you guys on? Here's what things look like on my iPhone 6:

Unknown

This content has been removed.

Rad

Hello @Bernfrin and @Larre,

Thanks for reporting this issue :+1:

We were able to reproduce this issue on iPad, so we created an internal bug.

Thanks!

ref: OPI-3035

Larre

Hi @Rad -

OK, that's great... thanks! Just for completeness, I believe that I'm using a second generation original iPad.

Larre

Rad

Hi @Larre,

Thanks for getting back to us so quickly.

I tested it with an iPad mini 3 and it happens there too.

Best,

stukey

Hi @Rad - I am also seeing this issue on my iPad Air 2 with iOS 9.0.1 when using the 1PW extension. I also see it when using the 1PW main app in slide over on the iPad - the password field is tiny and squished even though there's room to display a much wider password field.

AGAlumB

@stukey: Thanks for confirming that! We'll see what needs to be done to get this working more consistently across size classes. Cheers! :)