Chrome 27 (dev, Canary) rendering issues

khad
khad
1Password Alumni

There was a known issue in the current builds of Chrome 27 (the non-stable developer/Canary branch). It looks like whereas we used to be able to just reference the popup.html file in our iframe and get all its resources whitelisted "for free", now they have to be manually referenced in the manifest. It was a relatively simple but tedious fix but is now available in the beta channel of the 1Password Chrome extension.

The fix should be in the stable channel by the time Chrome 27 reaches the stable channel if not sooner. If you need to use beta/dev browser builds, you might also want to use the beta 1Password extension so you get these sorts of fixes as soon as possible. That said, we strongly recommend using stable browser builds for the best experience. Please see below for more details.

Non-Stable Browsers

1Password supports the stable builds of Safari, Chrome, and Firefox. While we can't guarantee that 1Password will work with Beta, Dev, Nightly, Canary, or other birds or browsers, we make every effort to maintain compatibility as browsers go through their various development and release cycles. Sometimes, a change comes along in a prerelease browser build that requires a change in the 1Password extension. If you're on the bleeding edge of browser releases, there may be a time when 1Password isn't compatible with the latest and greatest non-stable release of your favorite browser.

Rest assured, we monitor the development of Safari, Chrome, and Firefox very closely. We vigorously test each release for 1Password compatibility. We always recommend using the stable releases of each browser, particularly if you don't want to use a beta version of the 1Password extension or experience temporary incompatibilities. In general, prerelease browser builds are for testing new features and ensuring compatibility rather than daily browsing. For instance, we test development versions of browsers so we can be sure 1Password will be compatible as the release moves through beta and into the stable channel.

If you're having trouble with the latest stable release of your browser, please let us know! If you're using a beta, development, or other prerelease build, please know we're working hard on it and we'll have an update (usually a beta first) to restore compatibility soon.

This discussion has been closed.