Signing back into the Community for the first time? You'll need to reset your password to access your account. Find out more.
Forum Discussion
Former Member
3 years ago[USO] Button detection aborting due to timeout.
Hi,
I notice this error when 1password is active, and the button on the taskbar is clicked
[USO] Button detection aborting due to timeout.
When I disable the addon, this error is no longer present
I have the latest version of Chrome
1Password Version: Not Provided
Extension Version: 2.5.1
OS Version: Not Provided
Browser:_ Chrome
Referrer: forum-search:[USO] Button detection aborting due to timeout.
- francislavoieOccasional Contributor
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 callingconsole.info('[USO] Button detection aborting due to timeout.');
Putting a breakpoint on this and triggering it shows the stack trace, it's from thefocusin
event registered withdocument.body.addEventListener('focusin', this.handleDomEvent)
, which callsfindUsoProviders
, which calls a minified function namedHa
, which has a hugeif
statement with ane.forEach
and inside thatif
body is theconsole.info
.As others have said,
console.info
should not be used here. Useconsole.debug
instead. Or better, only print logs like this if some option is selected in 1Password extension settings. - Former Member
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 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!
- Former Member
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.
- Former Member
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.
- Former Member
Came here just to say that this was driving me nuts, I was developing an app thinking that this error was coming from either the library I was using or from a hidden event listener in my code. Turns out that it was from 1password specifically on the input type=password element! A better handling of the error would be great so atleast we can figure out that its from 1password.
- Former Member
Still happening and ditto to above. Please don't pollute the console with cryptic plugin messages....
- Former Member
Same problem. As others have already said, for web developers, these messages pollute the console log and are frustrating. At the very least you should change them to console.debug() events so they only appear when Verbose is selected.
- RoenfeldtOccasional Contributor
@Joy_1P thank you for trying to help me out! I've just replied to your support email :)
- Former Member
Currently the error with the button is shown, when I login on a WordPress site then open 1password by clicking the icon in the toolbar
Then click "Autofill" on the top right, the after the fields are populated, then select "submit", the screen is refreshed and then after a few seconds it is shown. It appears to me, that "button" is defined twice and closed by maybe WordPress. So the solution would be to rename the button in 1Password - Former Member
Next log does contain the error again!
main.js:1 [Violation] Added non-passive event listener to a scroll-blocking 'touchmove' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
value @ main.js:1
value @ main.js:1
value @ main.js:1
o @ main.js:1
(anonymous) @ main.js:1
11:44:53.920 polyfills.c50a757f6f682134.js:56 [Violation] 'message' handler took 421ms
11:44:54.012 injected.js:17 [Violation] 'setInterval' handler took 55ms
11:44:54.353 injected.js:17 [USO] Button detection aborting due to timeout.
11:44:54.354 injected.js:17 [Violation] 'setInterval' handler took 151ms
11:44:54.354 [Violation] Forced reflow while executing JavaScript took 50ms