Bitwarden Vault not autolocking
-
Bitwarden vault is not autolocking in Vivaldi (snapshot and stable), it works fine in Firefox or other Chromium browsers including Opera, Chrome, Brave and Edge.
Steps to reproduce:
- Install Bitwarden from webstore
- Set an autolock interval
- Use it and wait for the specified time
Actual result:
The vault is not autolocking after the specified timeExpected result:
The vault should lock automatically without user interaction. -
I have mine set to autolock on "On system lock". This works perfectly fine. However, if I change it to autolock based on time it doesn't seem to lock at all.
Please note, though, that this might not be a bug in Vivaldi but a bug in Bitwarden, so I suggest you also report it to Bitwarden.
(And for Vivaldi, have you reported it using the Bug Report Form? Can you post the VB number here?
)
-
@Komposten yes, VB-65756
-
@Gwen-Dragon found this https://github.com/bitwarden/browser/issues/1037#issuecomment-569672167
-
@Gwen-Dragon said in Bitwarden Vault not autolocking:
@victorbayas Thanks for hint to this bitwarden bug report, i updated Vivaldi bug tracker entry.
Thx
-
@Gwen-Dragon That's only so that the Bitwarden Android app supports the Vivaldi Android Snapshots.
-
Is this an issue Vivaldi is investigating? I would like to continue using it, but I really need Bitwarden's auto-lock feature to work.
-
@Gwen-Dragon Ok, thanks. Such a shame, this is one of the reasons I cannot fully commit to Vivaldi.
-
@Gwen-Dragon almost a year has passed and still no fix
-
@victorbayas I know, this is disappointing, but with small teams like this, some bugs just don't get the priority. I guess it only affects a small number of users.
-
I've been trying a lot to use Vivaldi as my main browser, but the devs' neglect of reports just discourages. Several bugs reported and no treaties...
This Bitwarden bug has complaints and was reported in 2019 by 2 users who came from Bitwarden's github, where they debug and pointed out the problem and still no fix... -
@fernandoccandidoo Vivaldi presumably has thousands of bug reports and thousands of feature requests. They can't fix everything so they have to prioritise based on popularity, severity and difficulty, and this bug is probably not severe or popular enough to warrant any kind of immediate attention.
Plenty of people have bugs from 2015 that still haven't been fixed for the same reason.
-
Ppafflick moved this topic from Extensions on