keepassxc-browser icon indicating copy to clipboard operation
keepassxc-browser copied to clipboard

https://sourceforge.net/auth/pwd_expired_change

Open stdedos opened this issue 1 month ago • 3 comments

Have you searched for an existing issue?

  • [x] Yes, I tried searching and reviewed the pinned issues

Brief Summary

Image

Here, I see two things wrong:

  1. Autocomplete fills field #3, instead of #1
  2. Password prompts from the extension autocomplete an entry even if you are typing a new password, and
  3. ... (the extension?) automatically moves you to the next field, and
  4. Field #3, even though you are typing a new password, after a small while it autocompletes one (the only one) of your entries, overwritting what you manually typed

Subissue of https://github.com/keepassxreboot/keepassxc-browser/issues/2386

Search: https://github.com/keepassxreboot/keepassxc-browser/issues?q=is%3Aissue%20sourceforge

Expected Versus Actual Behavior

No response

Steps to Reproduce

  1. Visit https://sourceforge.net/auth/pwd_expired_change (idk how can you achieve that, or if a password reset leads you to the same / similar form)
  2. Try to change your password

KeePassXC-Browser Debug Information

global.js:172 [Debug observer-helper.js:224] KeePassXC-Browser - Input fields found:
17:56:56.674 global.js:175 (2) [input#w-512.pw.tooltipstered, input#w-512.pw2.tooltipstered]
17:56:56.674 global.js:172 [Debug keepassxc-browser.js:353] KeePassXC-Browser - Login field combinations identified:
17:56:56.675 global.js:175 (2) [{…}, {…}]
17:56:56.730 global.js:172 [Debug observer-helper.js:224] KeePassXC-Browser - Input fields found:
17:56:56.730 global.js:175 (2) [input#w-512.pw.tooltipstered, input#w-512.pw2.tooltipstered]
17:56:56.730 global.js:172 [Debug keepassxc-browser.js:353] KeePassXC-Browser - Login field combinations identified:
17:56:56.730 global.js:175 (2) [{…}, {…}]
17:56:56.739 global.js:172 [Debug observer-helper.js:224] KeePassXC-Browser - Input fields found:
17:56:56.739 global.js:175 (2) [input#w-512.pw.tooltipstered, input#w-512.pw2.tooltipstered]
17:56:56.739 global.js:172 [Debug keepassxc-browser.js:353] KeePassXC-Browser - Login field combinations identified:
17:56:56.739 global.js:175 (2) [{…}, {…}]
17:57:03.417 global.js:172 [Debug observer-helper.js:224] KeePassXC-Browser - Input fields found:
17:57:03.417 global.js:175 (2) [input#w-512.pw.tooltipstered, input#w-512.pw2.tooltipstered]
17:57:03.417 global.js:172 [Debug keepassxc-browser.js:353] KeePassXC-Browser - Login field combinations identified:
17:57:03.417 global.js:175 (2) [{…}, {…}]

KeePassXC - 2.7.11
KeePassXC-Browser - 1.9.10
Operating system: Win64
Browser: Chrome/Chromium 117.0.0.0

stdedos avatar Nov 30 '25 16:11 stdedos

I worked around this by disabling

Image

stdedos avatar Nov 30 '25 16:11 stdedos

My 2 cents as a user, not a web developer. Unless all sites across the internet tag their form fields in a consistent manner allowing KPXC to distinguish between old/new password fields, I wouldn't expect KPXC to handle this situation gracefully.

Have never had autofill turned on. Not surprised it "misbehaves" a bit in this instance. Would guess there is no clean/consistent way to handle this. Maybe when we get AI-powered KPXC it can handle this for us! (kidding)

baekelite avatar Dec 10 '25 18:12 baekelite

We just try to guess the combo using a couple of different methods. Sometimes it obviously fails. Maybe AI could point to developers to use standards (almost not kidding here).

varjolintu avatar Dec 10 '25 19:12 varjolintu