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

Cycle through logins is getting stuck in a loop, repeating some and skipping others #4201

Closed
2 tasks done
luckman212 opened this issue Dec 8, 2022 · 4 comments
Closed
2 tasks done
Labels
browser Browser Extension bug

Comments

@luckman212
Copy link

Steps To Reproduce

Problem

  1. Go to a website that has multiple logins saved

example (microsoft.com):

  1. Use your "Auto-fill the last used login for the current website" hotkey to repeatedly cycle through the logins
  2. Note that there is no rhyme or reason to the sequence.
  • it is not alphabetical by Name
  • it is not alphabetical by Username
  • it does not appear to be based on "order saved in the vault"
  • it is not "cycle through logins in vault A, then proceed to vault B, C..." etc

Often (for me anyway) it appears to get stuck cycling between the same 6-7 logins and omits entirely the other 30+.

Sometimes, when pressing the hotkey, it just fills in the exact same login that was previously filled.

Very frustrating feature!

My suggestion

The feature should work like this:

  • Pressing the hotkey auto fills the LAST USED login for that site.
  • If the hotkey is pressed AGAIN, then index all the logins alphabetically A-Z by NAME OF THE BOOKMARK and begin cycling from the first one.
  • There should really be a hotkey for cycle BACKWARDS in case we press the key quickly and go 1 or 2 too far, instead of needing to reach for the mouse...
  • There should be a checkbox/preference something like
    • Omit Logins From Shared Vaults from auto-filling via hotkey

Expected Result

Cycling through logins should be deterministic.

Actual Result

???

Screenshots or Videos

If the developers want a video of this happening, I am happy to submit one privately, but due to the sensitive nature of the content I can't post it here.

Additional Context

Related (when the cycle feature was added): #956

Similar bugreport: #1392

Operating System

macOS

Operating System Version

13.0.1

Web Browser

Chrome

Browser Version

108.0.5359.98

Build Version

2022.10.1

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
@luckman212 luckman212 added browser Browser Extension bug labels Dec 8, 2022
@luckman212
Copy link
Author

luckman212 commented Jun 7, 2023

Has anyone looked at this or considered the points I outlined in it?

This continues to be the most frustrating thing about Bitwarden that I bump into Every. Single. Day.

Related forum threads:

@dwbit
Copy link
Contributor

dwbit commented Jun 8, 2023

Thanks for sharing an update, can you confirm what version number you are currently running?

@luckman212
Copy link
Author

luckman212 commented Jun 8, 2023

2023.5.0

But this bug has been there for months (perhaps years)

@TroyBW
Copy link

TroyBW commented Jul 14, 2023

Hi there,

When cycling through login items, the order is determined chronologically, by the last time the item was used. This ordered list can be visualized by clicking on the Bitwarden browser extension and looking at the "Tab" view, as the items are ordered in the same manner there.

We use GitHub issues as a place to track bugs and other development related issues. If you'd like to submit a feature request for the list of autofill items to be ordered alphabetically, the Bitwarden Community Forums has a Feature Requests section for submitting, voting for, and discussing requests: https://community.bitwarden.com/c/feature-requests/

Please sign up on our forums and search to see if this request already exists (https://community.bitwarden.com/signup). If so, you can vote for it and contribute to any discussions about it. If not, you can re-create the request there so that it can be properly tracked.

This issue will now be closed. Note that the “Closed as not planned” status is for internal tracking purposes only, please do not hesitate to send us your suggestions to the forum.

Thanks!

@TroyBW TroyBW closed this as not planned Won't fix, can't repro, duplicate, stale Jul 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
browser Browser Extension bug
Projects
None yet
Development

No branches or pull requests

3 participants