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

Character loss when typing into search box #4191

Closed
1 task done
counterpoint opened this issue Dec 6, 2022 · 3 comments
Closed
1 task done

Character loss when typing into search box #4191

counterpoint opened this issue Dec 6, 2022 · 3 comments
Labels
browser Browser Extension bug needs-reply Closes issue after 14 days if no reply from OP

Comments

@counterpoint
Copy link

Steps To Reproduce

Click on the browser icon. By default the cursor is in the search field. Type a word at normal typing speed (in my case about 50 words per minute). For example, “PayPal”.

Expected Result

Passwords for PayPal accounts are shown.

Actual Result

The software is attempting matches as each character is typed, but in the process, characters are lost. So after typing “PayPal” the box may show “Payal”. No match is found.

Screenshots or Videos

No response

Additional Context

I don’t want to type slowly, waiting for search to operate on each character, that is an unnatural thing to do. In around a second, I can type enough to be confident of finding what iam looking for. Except that if a character is lost, the search fails completely even though what I typed was correct.

Operating System

Linux

Operating System Version

Recent

Web Browser

Firefox

Browser Version

Current

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.
@counterpoint counterpoint added browser Browser Extension bug labels Dec 6, 2022
@luckman212
Copy link

luckman212 commented Dec 8, 2022

This has been an issue for many months—close to a year now. I reported the original issue #2371. Since then others have also reported similar issues. Example: #4128

It's annoying because they keep closing it as "fixed" when clearly it's not.

@djsmith85
Copy link
Contributor

Hi @counterpoint and thank you for your report.

This was previously reported with #2371. With #3680 it has also received a fix, the changes made there just got released with 2022.12

@luckman212: Issues get closed when a PR gets merged. This does not mean, those changes are available straight away. There's also a comment on the actual PR.

Please test out the changes with 2022.12 and report back if the issue has been resolved/behavior has improved.

Kind regards,
Daniel

@djsmith85 djsmith85 added the needs-reply Closes issue after 14 days if no reply from OP label Dec 19, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Jan 3, 2023

We need more information before we can help you with your problem. As we haven’t heard from you recently, this issue will be closed.

If this happens again or continues to be an problem, please respond to this issue with the information we’ve requested and anything else relevant.

@github-actions github-actions bot closed this as completed Jan 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
browser Browser Extension bug needs-reply Closes issue after 14 days if no reply from OP
Projects
None yet
Development

No branches or pull requests

3 participants