bobn4907
(bob)
February 20, 2024, 12:42am
1
So this is probably something I am failing to understand.
I can set clip-board time out to some value and whatever it is not available after the set time as is specified which works as designed.
however, if you invoke multi-paste, all your previously copied passwords, and anything else is easily seen.
to me this seems like a major flaw. am i missing something
grb
February 20, 2024, 4:30am
2
What operating system are you using, and is “multi-paste” a clipboard history feature in the operating system, or have you installed some third-party clipboard manager app?
FYI, as of November, 2023, Bitwarden is not expected to store any copied passwords in the Windows system clipboard history, as discussed in this thread on Github:
opened 08:26AM - 12 Nov 23 UTC
closed 01:37PM - 12 Nov 23 UTC
bug
desktop
### Steps To Reproduce
1. press the Copy Username or Password button
2. Check … the clipboard
3. The data is not saved.
### Expected Result
When a copy is made, it is saved to the clipboard.
(This worked until a few months ago.)
### Actual Result
The data is not saved.
And since pasting can be done with ctl+v, it is simply not saved to the clipboard.
### Screenshots or Videos
_No response_
### Additional Context
_No response_
### Operating System
Windows
### Operating System Version
win11
### Installation method
Direct Download (from bitwarden.com)
### Build Version
2023.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.
bobn4907
(bob)
February 20, 2024, 11:02am
3
chromebook Version 121.0.6167.188 (Official Build) (64-bit). this is a function of the os
I did verify the behavior is the same for user names
bobn4907
(bob)
February 20, 2024, 11:12am
4
thank you. I determined it was one of my extensions causing the issue
grb
February 20, 2024, 3:02pm
5
Interesting — thanks for the update. If you don’t mind sharing which extension it was, that information may be helpful to future readers of this thread who are experiencing a similar issue.