[USO] Button detection aborting due to timeout.

I just upgraded from 1Password 7 to v8 (and the respective browser-addon, v2.10.0 in Firefox) and can confirm this issue. It happens upon page loading but also when clicking into or leaving any input (of type text) field on the page. It's filling up the console.

Very annoying.

Likewise; web dev here and recently updated 1Password 7 to 8. Chrome Version 114.0.5735.133

[USO] Button detection aborting due to timeout. message permanently in the console while I'm working. Pretty annoying - would be good if you could disable, or at least add it's removal as an option in the Developers section of the prefs.

Hey @rezelute @me_and_myself @gummidge I've tried reproducing this behavior but I do not get the messages mentioned in this thread in my console. Moreover, @Roenfeldt also let us know that they no longer see the messages either. So I'm curious about what's happening over on your end.

Could you all share the steps that trigger the messages and then share a screenshot or copy over the messages to a reply so that we can review them? Additionally, you can provide those details to us via email, where we would be able to dive deeper into what's happening in your browser specifically.

If you send those details via email, please make sure to address the email to mailto:support+forum@1password.com. With your email please include:

• A link to this thread: https://1password.community/discussion/136379/uso-button-detection-aborting-due-to-timeout#latest
• Your forum username: ________

You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks!

I'm also seeing these in my app's logs. Unfortunately I can't provide access to the app to replicate it because of privacy reasons.

Here's what triggers it though. When a modal window is opened (div overlaid on the entire screen) it shows the log. I see the log is coming from injected.js, specifically calling console.info('[USO] Button detection aborting due to timeout.'); Putting a breakpoint on this and triggering it shows the stack trace, it's from the focusin event registered with document.body.addEventListener('focusin', this.handleDomEvent), which calls findUsoProviders, which calls a minified function named Ha, which has a huge if statement with an e.forEach and inside that if body is the console.info.

As others have said, console.info should not be used here. Use console.debug instead. Or better, only print logs like this if some option is selected in 1Password extension settings.