[Bug] Sidebar pages in Vivaldi browser get broken dark theme

Bug Report

Bug Description

All pages in the sidebar in the Vivaldi browser get some kind of partial dark theme. (Probably since last update?)

Website Address

Any, but it must be in the sidebar in the Vivaldi

Steps To Reproduce

• Launch Vivaldi
• Install Dark Reader
• (optionally) set Dark Reader to “Disabled on all websites by default”
• Add any page to sidebar panel (e.g. Instagram, Duolingo…)

Expected Behavior

I’d expect Dark Reader to not work in the sidebar at all since extensions (like uBlock etc.) usually don’t work there. And it didn’t work there until today. But if it does work, it should display websites correctly and also adhere to Dark Reader settings.

Actual Behavior

Websites get dark background, white text, but lot of images are missing (on Instagram and Duolingo). I also changed DR settings to “Disabled on all websites by default” and even non-whitelisted pages in the sidebar have this broken dark theme anyway.

Screenshots

Duolingo missing all the icons for the lessons.

System Information

• OS: Windows 10 Pro 20H2 64-bit
• Browser: latest Vivaldi 4.2.2406.48 64-bit
• Dark Reader Version: 4.9.35

Additional Context

I didn’t have this issue today morning. I suppose the extension got updated and now I can’t use pages in sidebar. According to DevTools, pages in the sidebar have this (at least) one element from Dark Reader extension injected: <style class="darkreader darkreader--fallback" media="screen">html, body, body :not(iframe):not(div[style^="position:absolute;top:0;left:-"]) { background-color: #181a1b !important; border-color: #776e62 !important; color: #e8e6e3 !important; } html, body { opacity: 1 !important; transition: none !important; }</style> Deleting this element manually in DevTools fixes the problem, until next page load, obviously.

I can also see this log in the Console of the Dark Reader extension, not sure if it’s relevant to the issue:

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'id')
    at reply (index.js:2843)
    at index.js:2853

[bershanskiy]

Thanks for info.

I see the version in Chrome extension store is now updated however it didn’t fix the problem (at least for me).

Current released version, 4.9.36, has this bug, so this is expected.

The version you told me to test still works fine and fixes the problem.

Thanks for confirming.

Is there a difference between them?

PR #6858 fixes the problem. It was not included in 4.9.36 (because it landed after 4.9.36 was released), but the next version (4.9.37) will have the fix.

[mateuszkozakiewicz]

Hello, I see the version in Chrome extension store is now updated however it didn’t fix the problem (at least for me). The version you told me to test still works fine and fixes the problem. Is there a difference between them? I have the extensions configured the exact same way, removing it and reinstalling to reset the configuration doesn’t help.