Extension detection of the current page is buggy
I'm running into two but probably related issues with 1P4 Mini.
First, if 1Password is locked, the vast majority of the time after unlocking the Mini window doesn't pick up the currently active page. It's as if it was opened from outside a browser context such as in the Finder. If I close it and re-invoke it, it works as expected.
However, sometimes it requires a second open of Mini to detect the current page, even when it's unlocked. It always works after the second time. I assume the browser extension is injecting some JS into each page. It makes me wonder if the page visually looks loaded, but the 1P4 JS hasn't had a chance to run yet? If that's the case, I don't see a good solution, other than perhaps adding a loading indicator and automatic refresh of some kind to 1P4 so I don't have to hit the keyboard shortcut again.
I've had both of these issues happen in Chrome 30 and Firefox 27.