Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Solved
1Password extension chokes on page with a large SELECT menu
I am using Chrome on a Chromebook:
Google Chrome 140.0.7339.229 (Official Build) (64-bit)
Revision fb1d11e56485bc88bdb9a81c261a212abc92d5a4-refs/branch-heads/7339@{#2791}
Platform 16371.61.0 (Official Build) stable-channel atlas
1Password Browser extension: 8.11.12.27
tl;dr the 1Password extension causes pathological performance degradation on a particular website I use, specifically on a management page which lists a set of user accounts. I can't say exactly when this started happening, but some time in the last several weeks (so unfortunately, no idea if the change occurred as the result of an update to the extension or if there was some change on the web site)
I can reproduce the issue using the following minimal HTML page snippet as a starting point/base case:
<!DOCTYPE html>
<html>
<head><title>test page</title></head>
<body>
<select name="userid" size="10">
<option value="1">value1</option>
<option value="2">value2</option>
<option value="3">value3</option>
<option value="4">value4</option>
<option value="5">value5</option>
<option value="6">value6</option>
<option value="7">value7</option>
<option value="8">value8</option>
<option value="9">value9</option>
<option value="10">value10</option>
</select>
</body>
</html>
If you save this to a location where it can be served up by a browser for 1P to interact with it, it all works, so far so good. You can click around in the select menu and select different names.
Now, increase the number of option values to 9000 (yes, this is a terrible user interface, and no, I have no control over the website :-( I am just someone who has to interact with it, and sadly any change request is likely to get ignored by those who are responsible for it)
When the above test page is increased to have 9000 values, on my system it is super slow to load, and if you try to click into the select menu, it takes an extremely long time until the item becomes highlighted, if at all; often the page just wedges completely and eventually Chrome pops up the "do you want to wait for this page to finish loading or exit" dialog. (With an intermediate number of values, say 2 or 3 thousand, it is noticeably slow but you can still click around in the select menu and have it respond, albeit sluggishly)
- I have seen this community discussion about using the context menu and selecting "Hide on this page". It doesn't help :-(
- I have seen the https://developer.1password.com/docs/web/compatible-website-design/#ignore-offers-to-save-or-fill-specific-fields about using "data-1p-ignore" or "data-op-ignore" attributes in the HTML source, but as I have no direct control over the source of the web site, I tried writing a TamperMonkey script as described in this community discussion -- viewing the page source with my script enabled confirms the attributes are being injected, but it still doesn't help
And unfortunately, this particular page is served from the same domain as other pages for this site like the login page where I do not want to disable 1P, so I can't just disable the entire domain.
So, two feature-request/bug report items:
- if you could have an explicit denylist that is editable from the extension settings (the user should not be forced to first visit a page which may not even be usable/loadable in order to use a context menu). Search does turn up existing discussions requesting this, but the handful I have clicked through on were all closed with the suggestion to use the "Hide on this page" context menu item, but that does not help here as discussed above
- I thought this was because 1P wants to inspect a field with name="userid" but even changing "userid" to "lol" or "foobar" or "zzz" makes no difference to the behavior, but regardless should 1P even be scanning SELECT elements at all? I guess it needs to for the form fill behavior. Still, while 9000 elements is pretty silly, it's not so many that it should cause software to choke, and certainly not until the user actually asks 1P to "remember" the form entries.
I will readily concede that this all sounds pretty contrived -- if I received this bug report I would laugh at it too -- so if the answer is "yeah, this is too much of a bizarre one-off, and we're not going to do anything about it" I can accept that :-) but meanwhile, are there any other potential workarounds I am missing, other than disabling the 1P extension when I visit this page?
Hello Zorak! 👋
I'm sorry that you were seeing performance issue when using 1Password in Chrome. Our team has indeed released performance fixes and improvements in the latest stable version of 1Password in the browser (8.11.16 or later).
I'm happy that the improvements resolved that issue that you were seeing as well. If you run into the issue again then let me know and I can help further.
-Dave
FS-3827
2 Replies
- 1P_Dave
Moderator
Hello Zorak! 👋
I'm sorry that you were seeing performance issue when using 1Password in Chrome. Our team has indeed released performance fixes and improvements in the latest stable version of 1Password in the browser (8.11.16 or later).
I'm happy that the improvements resolved that issue that you were seeing as well. If you run into the issue again then let me know and I can help further.
-Dave
FS-3827
... well, whatever this was, it's resolved now.
Chrome: 141.0.7390.126
1P extension: 8.11.16.35
as before, I haven't even tried the site w/o disabling the extension in a while, so no idea which of the two updates did anything, or if it was just sunspots or something /shrug
