Https error dialog comes up in main app instead of browser

Options
Quantumpanda
Quantumpanda
Community Member
in Mac

I found a really weird issue today. I was updating a web site password, and the browser popover had a warning about the site being set as http rather than https. I clicked on the button to use https, and the extension seemed to freeze—it stopped responding to clicks completely. I quit the browser, but the popover stayed open and frozen. I tried to quit 1P Mini, but the menu icon from which you can quit was not responding to clicks. I went into the main 1P app to see if I could quit everything from that (I normally leave the app open, because reasons), and found that an error dialog indicating that the site in question did not appear to support https was there. I closed the dialog, and the frozen popover started responding again.

My concern is that while the error was prompted by an action in the browser, the error dialog did not appear in the browser, nor did it bring the app in which it appeared to the front. That is undesirable behavior, as the user doesn't immediately see that an error came up and so has to hunt to figure out that it's an error dialog that froze the extension and not a bug or crash. Yes, the error beep sounded, but without a visible error message, the user doesn't know what generated the beep. Please fix this so that the error comes up in the browser, or failing that, at least brings the app to the front to show the error dialog immediately.

1Password Version: 7.4.1 (70401002)
Extension Version: 4.7.5.90 (for Opera)
OS Version: macOS 10.15.2
Sync Type: Dropbox

Comments

  • ag_ana
    ag_ana
    1Password Alumni
    Options

    Hi @Quantumpanda!

    My concern is that while the error was prompted by an action in the browser, the error dialog did not appear in the browser

    I think this is because the data is stored in the app, not in the browser extension, which simply gets the data from the app. So when you have to make some changes, you must do it in the app itself. After you agreed to change the website to https, the following error message came again from the app, not from the browser extension. I think this is the correct behavior.

    I will pass along your feedback though, thank you for taking the time to share this! :+1:

This discussion has been closed.