Prevent unsaved data from being lost

[kamran]

In some cases, unsaved data may be lost with the current version. Here are some scenarios that have happened to me:

Scenario 1

I keep Bitwarden on desktop open with an unsaved login, and it gets locked before I click “save” button. When I unlock it with pin, I see my unsaved data is lost.

Solution:

The editor page should remain open when bitwarden gets locked/unlocked.

Scenario 2

In the mobile app, I click the ‘back’ button while being on editor, hoping there will be a prompt asking if I want to save the note. But I get nothing instead, and my data is lost.

Solution:

When I click the ‘back’ button, there should be a prompt with these options: “Keep editing”, “Save”, “Don’t Save”.

[dh024 (David H)]

Possible duplicate to this request:

Persistent Bitwarden UI and maintain unsaved data

When creating a login I often want to copy paste information from elsewhere. This habit got ingrained when using LastPass. The Bitwarden extension doesn’t remember any state, however, so every time I click away the extension resets and I have to start all over again. It’d be nice if the extension remembered my location in other contexts, but I really really want it to save state while creating a login so that I can copy paste.

And this one:

Better behavior at vault timeout for unsaved changes

Unfortunatelly Bitwarden discards all unsaved changes without a warning at vault timeout. I want Bitwarden to auto-lock after one minute but some registration processes take more than a minute to complete. In my opinion Bitwarden should not be behind other password managers at this point. This “feature” leads to data loss and can lead to serious account lock out. Saving a draft of the changes requires deeper changes in Bitwarden. I would appreciate at least an option for the action automaticall…

OP: Please search for existing requests before creating new ones - I think everyone would appreciate that!

[kamran]

I think this post is partically duplicate of the posts you referred to. The “Scenario 1” is duplicate of the second post you cited. The “Scenario 2” and the first post you referred are not duplicates of each other, since one of them is about browser extension, the other being about mobile app.

[tgreer (Trey Greer)]

I’ve adjusted the existing posts to reflect all apps so we can close this thread and move discussion/votes to the existing topics.

Whatever mechanism we would introduce to save data would likely be used across all clients