A Quicker Way to Sign In

Pleonasm
Pleonasm
Community Member
edited July 16 in 1Password in the Browser

After completing a website sign in, a pop-up appears saying “A Quicker Way to Sign In: 1Password will now sign in automatically after autofilling your credentials.” Disabling the “Sign in automatically after autofill” setting in the 1Password browser extension does not prevent the same prompt from appearing again for the same website, after the browser’s history is cleared and the browser is closed.

Is there a mechanism to permanently prevent the “A Quicker Way to Sign In” pop-up from appearing on all websites? (Thank you.)

P.S.: I am using 1Password browser extension 2.25.1 in Safari 17.5 (private windows) on macOS 14.5.


1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser: Not Provided

Comments

  • zaid.alian
    edited July 5

    Hello @Pleonasm,

    My name is Zaid, and I am part of the 1Password Support. I'll be happy to help you.

    This notification is generated by the 1Password for Safari app, which utilizes the browser's history to store user-specific information.

    If you clear your browser's history or use a private tab, the notification may appear consistently because its settings are stored in the browser's history. Additionally, the indexedDB data (stored in "~/Library/Containers/com.apple.Safari/Data/Library/WebKit/WebsiteData/") of 1Password for Safari, which contains all the settings and processes to establish 1Password's functionality, will also be wiped out when Safari clears cache/history.

    Do you encounter this notification every time you autofill with 1Password during a regular Safari session where you haven't cleared your browser's history?

    -Zaid

  • Pleonasm
    Pleonasm
    Community Member

    @zaid.alian, thank you for your note. If the Safari history is not cleared, then the "A Quicker Way to Sign In" pop-up only appears the first time when signing into a website.

    However, as expected, the pop-up reappears whenever Safari’s history is cleared – and, becomes an annoyance since it must be manually closed in order to remove it from the browser’s window.

    Please consider finding a mechanism by which a user can optionally disable the appearance of this pop-up permanently and universally across all websites. In my opinion, a user who clears Safari’s history for privacy should not be forced to repeatedly experience the same pop-up. This annoyance did not previously occur, and I suspect it may be a recent "improvement" to the 1Password browser extension that perhaps can be reversed?

  • Hello @Pleonasm

    Thanks for following up with me. I appreciate it!

    I understand your concern. For users who regularly clear their browser's cache, this pop-up will continue to appear frequently.

    While I can't guarantee anything, I've logged your feature request internally to share it with the team. Our product team will review your feedback to assess its feasibility for inclusion in a future version of 1Password.

    Currently, you should be able to exclude extensions from being cleared when you clear your browser's history:

    1. Hold the Option key ⌥ while using Safari
    2. Click on History from the menu bar
    3. Select Clear history and Keep website data...

    image

    • For some context, Safari has a unique behavior where clearing the history also clears out the extensions cache. In contrast, other browsers typically only clear the browsing history and leave extensions data intact.

    Lastly, please feel free to provide your feedback to Apple regarding this unique feature, as it differs from how other browsers operate: https://www.apple.com/feedback/safari.html

    -Zaid

    ref: 2F40828092

  • Pleonasm
    Pleonasm
    Community Member

    @zaid.alian, thank you for your advice. I was unaware of the "option key" for Clear History in Safari. However, note that "Clear History and Keep Website Data" retains cookies, which is a privacy concern.

  • Dave_1P
    edited July 16

    @Pleonasm

    Thanks again for the feedback, I'm sorry that the suggested workaround isn't a complete fit for your use case. Hopefully the experience can be improved in the future for folks who regularly clear Safari's cache/history. 🙂

    -Dave