Chrome extension frozen pop-up

robgwin
robgwin
Community Member
edited November 7 in 1Password in the Browser

This issue occurs every now and then: I'm filling out some web form and the 1password extension detects something that might be a new login or credit card etc and pops up the dialog to save the new item, but the dialog is frozen. I can't save, edit, or even dismiss it with the X. It's just stuck there. The only exception is the "new item" and "update existing" buttons work -- I can flip between those two views, but NO other UI elements respond. Only way to get rid of it is refresh the browser page.

(Also: Not sure if relevant, but I've only seen it happen in cases where I didn't actually have any use for it. For example, I typed something in an input called "expiration" and it thinks I'm entering a credit card. That's a whole other topic but just providing here in case it has anything to do with the freezing.)


1Password Version: 8.10.48
Extension Version: 8.10.48.25
OS Version: macOS 13.6.9
Browser: Chrome 129.0.6668.60

Comments

  • Hello @robgwin! 👋

    I'm sorry that 1Password isn't responding when you try to save an item. The next time that the issue occurs, I'd like to ask you to create a diagnostics report from 1Password in your browser:

    Sending Diagnostics Reports (browser extension)

    Attach the diagnostics to an email message addressed to support+forum@1password.com.

    With your email please include:

    • A link to this thread: https://1password.community/discussion/148835/chrome-extension-frozen-pop-up
    • Your forum username: robgwin

    You should receive an automated reply from our BitBot assistant with a Support ID number.  Please post that number here.  Thanks very much!

    -Dave

  • robgwin
    robgwin
    Community Member

    Ok, it happened again today and I sent in the diagnostics report: BAD-32331-285

    Although... I just realized something that may be relevant: I'm a web developer and I think maybe this is specifically happening while I'm browsing my web app locally. Maybe 1P is conflicting with webpack debug mode or something. Still annoying to me but I guess that wouldn't be a widespread problem...

  • @robgwin

    Thank you for sending in the diagnostics report, one of my colleagues will send you a reply via email as soon as they've finished reviewing it.

    To prevent duplication of efforts, I'll close this thread.

    -Dave

    ref: BAD-32331-285

This discussion has been closed.