fix: stop Chrome offering to save passwords on the UMAP EPS field#346
Merged
Conversation
The InvokeAI credential inputs in the album manager are password fields that live outside any <form>, so Chrome groups every form-less input on the page into one synthetic form and heuristically picks a "username" field for them — landing on the UMAP EPS number spinner and attaching the password save/fill prompt to it. Annotate the credential pairs with autocomplete="username" / autocomplete="new-password" so Chrome no longer guesses, and add autocomplete="off" to the EPS spinner to opt it out of autofill. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Clicking in the UMAP Cluster Strength (EPS) spinner made Chrome pop up its password save/restore prompt.
Cause
The InvokeAI credential inputs in the album manager (
newAlbumInvokePassword,edit-album-invoke-password) are realtype="password"fields that don't live inside a<form>. Chrome groups every form-less input on the page into one synthetic form, sees a password field in it, and heuristically guesses which other field is the "username" — its guess landed on the EPS number spinner.Fix
album-manager.html: annotate both credential pairs (new-album and edit-album) withautocomplete="username"/autocomplete="new-password". With the credentials explicitly annotated, Chrome no longer hunts for a username field elsewhere on the page;new-passwordalso stops Chrome offering stored passwords in those fields.umap-floating-window.html: addautocomplete="off"toumapEpsSpinnerto opt it out of autofill entirely.Testing
localhost:8050, the key icon may persist on old saved data until that entry is removed inchrome://passwords.🤖 Generated with Claude Code