Vivaldi browser and extension 2026.5.0 -- side panel keeps opening

Hi,

Since the update to 2026.5.0, the Vivaldi sidebar opens when I log out of Bitwarden.

Bitwarden automatically locks itself after a while. As soon as that happens, the Vivaldi sidebar opens. This has only been happening since the Bitwarden update to 2026.5.0. Is this happening to you too?

Vivaldi: 8.0 Build 4033.35

Bitwarden Browser: 2026.5.0

Greetings

Hi, I have the exact same issue! I thought I’d accidentally changed some settings or was going crazy. It’s definitely not just you; they must have broken something with the latest update.

Thanks for reporting, just to double check, it sounds like you’re experiencing this issue previously affecting Firefox? Does this issue persist with a fresh installation?

The issue with Firefox sounds similar. I always keep the sidebar closed or minimized in Vivaldi. I don’t really use it at all. Whenever BW locks up, the sidebar pops up immediately. It’s annoying.
The same thing happens on another PC, where everything is basically a fresh install.
This has definitely only been happening since version 2026.5.0.

Yes, the issue sounds similar. However, when the sidebar pops up, a blank/white page (or rectangle) also opens from the Bitwarden icon. This also happens when manually clicking the Bitwarden icon in the sidebar.

The issue persists even with a fresh installation.

Thanks for confirmation, please either submit a Vivaldi specific bug report for the team to follow up on or share a detailed report directly with the support team.

I reported it now.

Same here with Vivaldi 8.0.4033.42 and Bitwarden 2026.5.1

:+1:

I’m seeing it, too, and I’ve added to the Github thread.

Bitwarden keeps opening the side panel, which is a blank disabled page. I keep trying to close it and remove the side panel button, but it eventually re-opens itself.

Side panel URI: chrome-extension://nngceckbapebfimnlniiiahkandclblb/sidepanel-disabled.html

Something must have changed in 2026.5.1. The side panel was merged last month in ā€œAutotriage merge candidate #20149ā€:

@XP1 I’ve just moved your post into this existing thread on the same topic. – See above…

Hello!
Any solution yet?

The team is working on a fix that should be available for everyone soon.

It doesn’t seem to have been fixed in version 2026.6.0.