Level up your business security with free, on-demand training and certification. Explore 1Password Academy today →
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
