Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Native Password AutoFill Extension macOS
So one of the people in my family subscription for 1P relies heavily on iCloud Keychain. The nice piece about using the native autofill extension is entries from both show up together in-line. This happens on iOS (or if you use other password managers it secure by each provider but both are offered the same way together). in terms of migration and allowing those who wish to use both depending on the context. It would be nice to support the native autofill extension, but further it limits exposure or need for safari extension. Should someone not want to use or can't install the extension due to work policy or just rather not use safari extensions thanks. 1Password Version: 8.x Extension Version: Not Provided OS Version: macOS 12.6 Browser:_ Safari
1Password Chrome extension is incorrectly manipulating <code> blocks
The latest 1Password Chrome extension is incorrectly manipulating the DOM within <code> blocks on static pages. It looks it's using prism.js to try to add syntax highlighting to <code> blocks on the entire page. If you're using a static site generator to highlight code with a different library, it causes the display to break. Example: mkdocs, a popular documentation tool If you view the documentation for customizing Mkdocs material (https://squidfunk.github.io/mkdocs-material/customization/) with the extension enabled, you'll see that the YAML example at the top is not highlighted (it should be). Under the hood, if you inspect its DOM, you can see that it's been rewritten with prismjs classes. If you disable the extension, it is highlighted: This is likely to impact a number of documentation sites in the tech community.
Wildcard implementation in website property of Login Item
website property inside 1Password Login Item is a great feature which helps to automatically detect and auto fill username and password into the form fields. What's great about it and what's already implemented: You can actually create multiple website properties and still any of the matching websites will work You can set the domain to the website property and any subdomain of that domain will work You can set the domain to the website property and any subdirectory of that domain will work However I can give an example from https://www.netlify.com/ (web deployment platform) which won't match with any of the above 3 features. Let's assume I am developing web application and I set my application url as https://some-app.netlify.app. Netlify has a greate feature to customize subdomains based on the different deployment strategies. For example if I am now working on new github branch and I create a PR #100, then Netlify automatically creates new deployment url https://deploy-preview-129--some-app.netlify.app which is not just a subdomain of netlify.app because there can be thousands of app in netlify, however this is slightly different customized subdomain of netlify with some predefined prefix. So what I would I like is implementation of some custom wildcard options for the subdomains like *sub.domain.com where I can have potentially anything in the place of wildcard *. 1Password Version: Not Provided Extension Version: Not Provided OS Version: Not Provided Browser: Not Provided
Chrome Extension Causes Unwanted Vertical Scrollbar by Injecting 1p-live-region Element
Title: 1Password Chrome Extension (v8.11.14.24) Causes Unwanted Vertical Scrollbar by Injecting 1p-live-region Element Hello 1Password Team, I’m encountering a layout issue triggered by the 1Password Chrome extension, which I believe was introduced in a recent update (within the last week or two). Below are the details: Environment: Device: MacBook Pro 15-inch, 2018 (macOS 15.6.1) Browser: Chrome 141 1Password Extension Version: 8.11.14.24 Issue Description: The page structure includes a root div inside the body with styles set to width: 100vw and height: 100vh, while the html element has width: 100% and height: 100%. Under normal conditions, the page renders correctly without any scrollbars. However, when an input field on the page is focused, the 1Password extension injects a new element into the body with the ID 1p-live-region. This element has a fixed height of 1px, which introduces an unwanted vertical scrollbar and breaks the intended layout. Steps to Reproduce: Load a page with a root div set to 100vw/100vh and html set to 100% height/width. Observe that the page displays correctly without scrollbars. Focus on any input field to trigger the 1Password extension. The 1p-live-region element is added, causing a vertical scrollbar to appear. Expected Behavior: The injected 1p-live-region element should not disrupt the page layout or cause scrollbars to appear. This issue seems to be a recent regression. I’d appreciate it if the team could investigate and resolve it. Thank you for your attention and hard work! Let me know if you need additional details or clarifications.
