Recent javascript slowness on input focus
Hi,
We have users with Windows 10/Chrome/1Password reporting a very slow browser experience when focusing a text input. Up to 3s to obtain focus into the input, which is locking the browser's main thread.
The page in question has a large number of inputs, (many hidden, nearly 2000). We maintain and control the page in question, and so we can make changes to this page, outside of reducing the number of inputs.
This is recently slow, and a new development within the last 30 days, roughly.
This focus delay does not occur when the 1password extension is disabled.
Ideally there would be a way to exclude this page or these inputs from 1password entirely.
1Password Version: 1Password for Windows 8.10.22 (81022040)
Extension Version: 2.18.2
OS Version: Windows 10 Pro 19045.3803
Browser: Chrome
Comments
-
I can confirm I am seeing similar issues that arose just recently.
The focus event is terribly slow, see chrome profile here:
https://app.screencast.com/mxFUZL4gJjGfM
1Password for Windows 8.10.22 (81022040)
Extension version
Version
2.18.1OS Windows 10/64
Browser:
Google Chrome
Chrome is up to date
Version 120.0.6099.110 (Official Build) (64-bit)0 -
Hello @fatica! 👋
I'm sorry that you're running into performance issues with 1Password when focusing fields on your webpage. So that the team can help further, I'd like to ask for a console log from your end: https://support.1password.com/cs/extension-console-log/
Attach the log to an email message addressed to
support+forum@1password.com
.With your email please include:
- A link to this thread: https://1password.community/discussion/143724/recent-javascript-slowness-on-input-focus
- Your forum username: fatica
- The URL of the specific page where you encounter the issue so that we can try to reproduce the problem.
You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!
-Dave
0 -
[#EUI-19571-689]
FYI, a very similar report here:
https://1password.community/discussion/comment/701865#Comment_701865
0