Protect what matters – even after you're gone. Make a plan for your digital legacy today.
browser extension
6533 TopicsSecurity settings were changed automatically somehow.
Short-time user (2 months). Everything was smooth until yesterday. All of a sudden, 1Password started asking me to enter my master password every time I started Edge (W11). Previously, it would only ask at long intervals (per the settings I had selected when I installed it). I looked, and many of my security settings had been changed to require this, including a setting to use Windows Hello, which (for several reasons), I never use (and cannot use). I put the settings back the way they were, but I need to understand how and why this can happen. If it's a result of a Windows update, I need to have a way to prevent it in the future. If it's a result of a 1Password update, I need to understand why the developers felt it appropriate to do so. Thanks.30Views0likes3Commentsin Chrome how do I disable autofill of Google Wallet items?
I have some passes, loyalty cards, etc. saved in my Google Wallet. Rather annoyingly, some recent change has caused a Wallet autofill menu to start popping up where it is not wanted, specifically, on the Delta login dialog: I cannot figure out how to disable this. If I go to chrome://settings/payments it shows that 1Password is managing auto-fill: I have also looked all over https://wallet.google.com/ and https://payments.google.com/ and related pages and cannot find any setting that would control this; I have tried disabling 1Password in the above dialog just to make sure I can toggle "Save and fill" off but that doesn't help. In fact, the pop-up menu in the first screenshot only appears when 1Password is enabled. If I disable 1P and reload the Delta website then that popup does not appear. This would seem to imply it is either under 1P's direct control, or a result of how 1P interacts in combination with Google Wallet. This is not a critical bug, since the 1P fill button is still clickable, and/or I can fill my DL creds from the 1P toolbar icon, but it is definitely an annoyance to have the loyalty cards popup in my face when I don't actually _ever_ want it to show up (if I want to autofill a loyalty number that badly I will simply create a 1P entry for it, I don't want to pull anything over from Google Wallet; and even though I can see how others might want that feature, (a) it should be toggle-able (b) wouldn't it be better to integrate the autofill into the existing UI elements instead of popping up a completely separate menu?)Solved119Views0likes4CommentsBring 'custom trusted browser' feature to Windows
Following on for the various Opera-related requests that are 'solved' with either 'use a supported browser' or 'solved on mac': please bring this feature to Windows. My personal motivation is Chrome's recent neutering of ad blockers, combined with the excessive use of Windows system notifications for feature advertisement by Firefox and Edge, and the pushing of Web3/crypto nonsense in Brave.Solved119Views1like10CommentsBug: 1Password Browser Extension and Standalone App connection problem
Hi, I recently noticed that 1Password's Browser Extension (Edge / Brave) have connection problem with the standalone app. Scenario 1: When I unlock the standalone app it does not unlock its browser extension app. And I have to enter the password again to unlock the browser extension's app. Scenario 2: When browser extension is unlocked it does not unlock the standalone app (which I believe was always the case, but I am not sure), but when I manually lock the standalone it does not lock the browser extension's app. Also, I noticed there is a "connection problem" from the browser extension app. I have reinstalled both browser extension as well as standalone but the issue is same, also for both EDGE and Brave browser. My current standalone version 1Password for Windows 8.11.18 (81118036)Solved51Views0likes4CommentsAutofill no longer works on HTTP pages; iOS shows white blank screen
I’m running into an issue where 1Password can’t fill on any http:// pages across multiple platforms, and on iOS it can even result in a white/blank screen when I try to fill. What’s happening iOS (1Password app + Safari extension): On http:// pages, 1Password cannot autofill. When I invoke 1Password to fill on an HTTP page, the 1Password UI becomes a white/blank screen. Chrome / Edge extension (desktop): Autofill does not work on http:// pages at all. macOS app / Safari (macOS): Same behavior — no filling on http:// pages. Expected behavior I understand HTTP is insecure, but I still expect either: autofill to work (possibly with a warning/confirmation), or a clear message explaining that filling is blocked on http:// pages — not a blank/white screen on iOS. Notes / why this matters These http:// sites are mostly local network / self-hosted services that don’t have HTTPS enabled yet (or are reachable only via LAN IP/hostnames). So “just use HTTPS” isn’t always possible. Also, I saw other reports that HTTP filling stopped working recently in some extension versions (people mentioned it worked again after downgrading), so I’m wondering if this is a regression. 1password.community Steps to reproduce (iOS) Open Safari on iOS and go to an http:// login page (example: http://[local-address]/login). Tap into the username/password field and try to fill with 1Password (AutoFill or Safari extension pop-up). Result: no autofill; in some cases the 1Password UI turns into a white/blank screen. My environment iOS: 26.2 1Password for iOS: 8.11.22 macOS: 26.2 1Password for macOS: 8.11.22 Browser: Chrome 143.0.7499.170 / Edge 143.0.3650.96 / Safari 26.2 (21623.1.14.11.9) 1Password browser extension: Chrome/Edge 8.11.27.2、Safari 8.11.22.27 What I’ve tried Restarted browser(s) and device(s) Updated 1Password apps and extensions Re-enabled / reinstalled the extension(s) Confirmed the Login item is correctly associated with the site Could you confirm whether filling on http:// pages is supposed to be blocked now, and if not, whether this is a known bug/regression? If you need diagnostics/logs, tell me what to collect and where to send them.Solved129Views5likes4CommentsConnection with Chrome & Suggested items
I have the following problem: When I press CMD+SHIFT+X (Quick access), it used to open a pop up with a list of passwords for the website I was browsing at the time. However, now Quick Access pop up now opens with only 2 items, which are not related to the website I'm browsing: I have reviewed all settings and everything is connected. After some research I have found that these 2 items happen to have Chrome as a connected app, like this: No other login item is connected to chrome. I need help to understand: Quick access should suggest items related to the website I'm browsing, right? Why are not all items connected to chrome?25Views0likes4CommentsHas something changed: http:// not filling in any more?
For passwords I have that are specifically http:// like on my own Lan, these aren't being suggested any more by 1Password extension in Brave. Anything https:// is working. And yes I have http:// set as the Website address. I'm sure this was working until very recently.Solved2.7KViews18likes40CommentsThe extension on Safari stays locked even when the app is unlocked.
Hi, the 1Password extension on Safari remains locked even if the app is unlocked, and I always have to click on the icon to unlock it (the connection between the app and the extension is regularly active). What can I check? 1Password Version: 8.10.56 Extension Version: 8.10.56.28 OS Version: Sequoia 15.2 Browser: Safari 18.2 (20620.1.16.11.8)104Views0likes6CommentsNew Browser extension comment
Hi, Just wanted to comment on something that I find annoying in the new browser extension. It ALWAYS uses the term "Sign in", yet I have the option to auto submit disabled therefore, it's not signing me in, but auto filling. I feel that if a user has the auto submit option disabled (like me), the wording should be changed to say "Auto fill" or something similar to actually indicate what will actually happen. Otherwise it's just misleading.26Views0likes3Comments