![]() * WebSocket hack: MozWebSocket is a DOM api, and therefore is not available in the main. We use a hidden frame to get access to WebSocket in our equivalent of main.js (code below) but perhaps there is a better way for us to get access to WebSocket? Thanks for any insights you can offer and for your patience! You can sign out of your 1Password account and remove the vaults associated with it from one or all your devices. If you rely heavily on 1Password, I'd recommend the upgrade, although that's entirely up to you. The latest 1Password in the Browser, while newer and better, does require a 1Password account to use. ![]() I haven't been doing much work on the 1Password extension myself lately, but in talking with the developers that do, it looks like the way we set up our WebSocket connection to the 1Password background process isn't compatible with e10s. Learn how to sign out of your 1Password account on Mac, Windows, iOS, Android, and Linux. ago Yep, this should do the trick for you. ![]() Hey, all, sorry for taking so long to respond to this thread. The responsiveness improvements are manifest. Minor aside, almost everything else about e10s is working gloriously. I'm guessing that the 1P developers just need to adjust their addon to compensate for this, but I thought I would file the bug anyway. Hypothesis… Given that 1Password is filling in form elements *and* triggering an animation, it seems almost guaranteed that it is accessing DOM elements from the chrome process. Note: I was experimenting with processCount I doubt it has an effect on this bug.ģ) Navigate to a website with a saved loginĤ) 1Password shortcut does nothing and the extension is not visible in the addon bar. To start, the LastPass browser extension auto logout feature has critical bugs. User Agent: Mozilla/5.0 (Macintosh Intel Mac OS X 10.9 rv:32.0) Gecko/20100101 Firefox/32.0 (Beta/Release)Ģ) Enable e10s (=true =true =8). Theyre pushing people to a 1Password-managed cloud sync system instead.
0 Comments
Leave a Reply. |