Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[JENKINS-28474] workaround chrome autocomplete issue #13

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Twiknight
Copy link

fix for https://issues.jenkins-ci.org/browse/JENKINS-28474.
Now autocomplete="off" does not work in some case.
Use autocomplete="new-password" will require a manually inputed new password

See:
http://stackoverflow.com/questions/15738259/disabling-chrome-autofill
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#attr-autocomplete

fix for https://issues.jenkins-ci.org/browse/JENKINS-28474.
Now `autocomplete="off"` does not work in some case.
Use `autocomplete="new-password"` will require a manually inputed new password

See:
http://stackoverflow.com/questions/15738259/disabling-chrome-autofill
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input#attr-autocomplete
@Twiknight
Copy link
Author

Twiknight commented Mar 8, 2017

This problem is fatal.
If you're autofilled with chrome, you may get locked outside Jenkins before you can get the system operation team to fix the config file from server side.

@fabriziocucci
Copy link

fabriziocucci commented May 11, 2017

I agree with @Twiknight, this problem is quite serious.

I've experienced the issue of being locked out from Jenkins.

Why there is no one even assigned to this?

@jtnord jtnord changed the title fix issue-28474 [JENKINS-28474] workaround chrome autocomplete issue May 17, 2023
@zbynek
Copy link
Contributor

zbynek commented Apr 5, 2024

Didn't @daniel-beck fix this in jenkinsci/jenkins@90e693b ?

@daniel-beck
Copy link
Member

That would be my expectation. I suggest we close this and the referenced issue saying we believe it's resolved since 2.205, and anyone who still experiences the problem should file a new issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants