Changing password for Zoom.us locks up browser tab

esquared
esquared
Community Member

When changing my password on Zoom.us, 1P8 offered to generate a new password, and then update the existing entry in 1P, but when I select "update", the browser tab locked up, forcing me to refresh the tab and perform the password update manually.

It might be that a dialog from the web page was behind the 1P8 update login dialog and the two were in conflict. Just a guess.


1Password Version: 8.8.0 / beta 80800183
Extension Version: 2.3.7
OS Version: macOS 12.4
Browser:_ Firefox 102.0.1

Comments

  • Hi @esquared:

    I wasn't able to immediately replicate this on Safari using 1Password for Safari 2.3.7. Are you still running into trouble with changing your password on Zoom? Let me know!

    Jack

  • esquared
    esquared
    Community Member

    Note that I was NOT using Safari, but Firefox and the FireFox plug-in version 3.2.7.

    Regardless, it is working functionally better now (Beta 80800215), but not flawlessly. The previous behavior is gone, but now it's not seamless, but it's a special case for Zoom. Zoom wants you to enter your new password once, and only then displays the "Confirm your new password" field, which doesn't get filled, obviously. At that point, I had to copy/paste the new password in manually.

  • Hey @esquared:

    My apologies for missing that. In this case, you can copy and paste from the 1Password pop-up, or drag the newly created password after saving the change from the 1Password pop-up right to the "Confirm Password" field.

    Jack

  • esquared
    esquared
    Community Member

    Thanks for the additional tips, @Jack.P_1P - I don't know to what extent you guys try to handle special cases like this, so perhaps this is one of those things that becomes "1Password handles updating passwords on Zoom.us better now" in some future release notes.

    That said, if it were my choice, I'd rather see some other features added to 1P before that fix (e.g. re-arrange fields, change field type)

This discussion has been closed.