Vault filters not honored after saving

[bwbug]

Steps To Reproduce

1. Open the browser extension to the Vault view.
2. Set one or more vault filters (e.g., Type, Folder, Collection).
3. Open any item in the search results.
4. Click Edit.
5. Click Save.
6. Click < (Back) to return to the Vault view.
7. Confirm that the filters that were enabled in Step 2 are still enabled.

Expected Result

The items displayed in the Vault view should still be filtered by the vault filters that were enabled in Step 2 (and that were confirmed to still be set in Step 7).

Actual Result

The Vault view is not filtered (other than by search terms, if any search was performed). The active vault filters are not honored.

Screenshots or Videos

Additional Context

The vault filters work as expected if Step 5 (clicking Save) is skipped in the "Steps To Reproduce".

Operating System

Windows

Operating System Version

No response

Web Browser

Chrome

Browser Version

No response

Environment Versions

Version: 2025.3.1

SDK: 'main (6008e90)'

Server version: 2025.3.3

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.

[S-Kakar]

Thank you for reporting this issue! We've added this to our internal tracking system.
ID: PM-19922

[pamperer562580892423]

@bwbug I'm not sure what your reference for the behaviour of the vault filters is - but if it is the "announcement" in the Release Notes, I would like to point out, that browser extension 2025.3.2 would be necessary for the new "persistence":

(See here: https://bitwarden.com/help/releasenotes/#2025-3-3)

PS: I see your point - and the bug. But I wanted to say: maybe it is already different with the changes coming with 2025.3.2?! Because before, "without persistence", I suspect, the cards filter still shown as "active" after the "save-action" may be the bug...

[pamperer562580892423]

I just tested this with the browser extension update 2025.3.2 on two different browsers and don't see this bug any longer, following your steps to reproduce @bwbug .

[bwbug]

This bug has nothing to do with persistence when closing/opening the extension — in all my tests, teh browser extension window was never closed. As mentioned in the "Additional Info", the vault filter settings are in fact honored when returning back to the Vault view after viewing an item (and even if entering the Edit view without saving any changes). The bug manifests only when editing an item from the filtered results and then clicking Save.

It is possible that the issue has been resolved in 2025.3.2, but the behavior in 2025.3.1 is definitely counter to expectations. I will wait and see how things change when the Chrome extension is updated.