Master Password Login Screen Issue

wkleem

Hi

The placement of the master password field looks odd with the shortened field too? It’s too high?

AGAlumB

Yep.

wkleem

Good luck trying to solve this one bug or two!

ag_ana

Thank you! :) :+1:

wkleem

Hopefully, Agilebits will be able to discover something before this thread gets locked. The first bug report in 2015 was completely forgotten. I am not optimistic for a quick fix and for 1Password 7 to finally be rid of the bug. For 1Password 8 then?

AGAlumB

I haven't seen any "bug reports" about this which included anything actionable, unfortunately. Bugs rarely get fixed by accident; more often, they need to be reproduced first in order to determine what the problem even is.

wkleem

Understood. Good luck. It still mystifies me that only I would see it and report it 4 years between then and now and nobody else noticed. That is it from me on this if I can’t discover any more details.

From 2015 :

ref: OPI-3099

AGAlumB

Thanks! Yeah, it is a bit perplexing.

wkleem

Happened again. Splitting keyboard had no effect after I saw this bug. I mostly used landscape mode for the iPad. I had the login text box active at the time, not just pulling down Safari Extension for filling userid/passwords. Touch ID is off for the Mini 5 and in the iPad 4 there was no Touch ID just a home button.

AGAlumB

Interesting. Thanks for the additional data point!

wkleem

Hi @brenty,

I hope Agilebits will solve this issue, not only for myself but for the community at large. The trigger, so far, seems to be landscape and that text box caret “|“ is visible? I seldom use portrait orientation.

I should use portrait orientation to see if I can trigger the bug.

An observation as to why it might only affect iPads. The extension in iPhone is at the bottom of Mobile Safari. The keyboard, when active, covers the extension, preventing it from being invoked.

AGAlumB

I'm sorry that this bothers you, but I don't see anyone else having this issue; and frankly it's cosmetic. All things being equal, it would be nice to find a solution, but we need to prioritize the things that help the most people. And there isn't actually anything we can do about this without first finding the cause. Sorry.

wkleem

All right then. Just alerting Agilebits. It does bother me a little which is why I reported the bug in the first place. Feel free to ignore it then as it is a low priority for you guys until someone where you are gets other reports finding it, if they find it.

I will assume it won't be fixed for the foreseeable future. It will be good but I won’t count on it.

ag_ana

We appreciate the report :) We are not ignoring the issue, we just have never been able to reproduce consistently and find a root cause for it.

wkleem

Thank you for clarifying and for putting up with me. Best of luck trying to solve it.

AGAlumB

:) :+1: