Question

1password input focus lag with lots of inputs

Forum|Forum|6 months ago
December 5, 2025
3 replies
254 views

I'm running into an issue where 1password seems to significantly slow down interaction with the webpage I'm working on. There's a ton of input fields of which most are hidden, I cannot lower the amount of inputs, in fact I have to increase the amount of inputs due to how the system works.

Every time I click on an input, the focus is delayed by ~200ms or so. The next time I select the same input field it's instant. 1password seems to do something that slows down the focus event.

I made a performance recording in firefox. I selected 3 inputs and after the 3rd on selected the same 3 in the same order with no slowdown. I've tried adding data-1p-ignore and autocomplete="off" but it didn't solve anything.

A

Anonymous

Hi @Linaori ,

Thanks for writing in, could you share a bit more information about which platforms and versions of the App, Browser Plugin you are using? also has anyone on your team experienced it testing?

Thanks!
Phil

L

LinaoriAuthor

Firefox 145.0.1 (64-bit)
Fedora 43, KDE Plasma 6.5.3
1password browser extension version: 8.11.16.35

Nobody else on my team has this issue (yet) because I'm still developing the page. For now I've disabled 1password on my local env, but that's obviously not a permanent solution.

Here's a list of the input amounts:

document.querySelectorAll(`input[type="text"]`).length;
2989
document.querySelectorAll(`input[type="checkbox"]`).length;
609
document.querySelectorAll(`textarea`).length;
1
document.querySelectorAll(`select`).length;
427
document.querySelectorAll(`option`).length;
5708

B

Benjiman

I am experiencing a very similar issue and am also interested in the solution

D

dsine

We have the same problem, even without many input fields.

Seems like the browser plugin searches for elements near text input fields as soon as they are being focussed (manually by clicking into the text input field or programmatically through JavaScript, or by the `autofocus` HTML attribute in `popover` elements) if the element was not shown before/on page load (like in popover elements or any hidden content).

Windows & Mac, Firefox & Chrome... doesn't matter, the plugin seems to do really heavy things as soon as a input is focussed - a browser plugin should really not cause such issues with standard code.

At least there should be a HTML attribute to completely disable the plugin code.

Here is a JSFiddle that shows the issue:

https://jsfiddle.net/dsine/dj4afgws/

Without the plugin, the button click takes 50 ms, and with 1200 ms.

L

LucasRoesler

Hi @1P_Phil I also ran into this issue today when new textarea elements are added to the DOM. With 1password disabled, the new element is inserted and rendered in <50ms, With 1password, it is over 200ms. This is only a single new element, no where near the number of inputs that Linaori mentions.

In my case it is a text field to leave a comment, definitely not autofillable. I have tried every documented way to disable this, but none work, the lag persists. At this point is seems like I need to replace the textarea with a div+JS. This feels wrong and like significant overkill, to simply avoid 1password.

Is there any update on potential workarounds to disable 1password from scanning these elements?

Sign up

1Password employees: Sign in with SSO

Login to the community

1Password employees: Sign in with SSO

Scanning file for viruses.

This file cannot be downloaded