Dark mode settings are not working for websites and dev tools

[MatPerito]

MatPerito last edited by

same issue here, gotta set dark mode or system default every time I open it

[NeonCatRider]

NeonCatRider last edited by

Same thing here

[thaoktk]

thaoktk last edited by

i got the same issue, pls give a hot fix, i don't want to work with light mode anymore

[gonzalesl]

gonzalesl last edited by

Seriously, is anyone working on this or no one literally cares?

[OldCrow69]

OldCrow69 last edited by leocg

After the last update, the dev tool panel is appearing in that nasty default Chrome color instead of dark mode.

Even after setting it, it returns to "System Preference" after a reboot.

To reproduce:

1.Restart PC
2.Open Opera
3. Press <CTRL>+<SHIFT>+<I>
4. Observer color scheme is Standard.
5. Set to a different color scheme.
6. Repeat steps.

OS=Windows Server 2016 (Amazon AWS Workspaces)
Logged in as Administrator

[BlasterLizard]

BlasterLizard last edited by

Same thing here... Can't deal with the light mode anymore. It's almost one month already.

[PandSkin]

PandSkin last edited by

Same problem here, if this doesn't get resolved soon im switching and I highly recommend anybody else having this problem to also do so, because its obvious how important feedback is around here.

[DeeLaw]

DeeLaw last edited by

The issue still persists on operaGX. The devtool window is light mode by default but when I check the theme option it is set to dark mode. Switching it to light then dark again makes it go into dark mode but it resets back to light mode on refresh. Please fix!!

Opera Version: LVL 6 (core: 113.0.5230.108)

[idlethumbs85]

idlethumbs85 last edited by

Having the same problem, raised as a bug with opera twice now and have seen no fix (surely this is a quick fix?!), as a web developer who has chosen Opera as my browser of choice it seems those who chuckled at me are being proven right. Back to chrome it seems....

[leocg]

leocg Moderator Volunteer last edited by

Known issue

[gonzalesl]

gonzalesl @leocg last edited by

@leocg Which means what? Are devs working on it, any ETA? Or it is just "known" and ignored?

[leocg]

leocg Moderator Volunteer @gonzalesl last edited by

@gonzalesl It means that Opera knows about the issue and it's in the tracker to be fixed.

[HenryBSilva]

HenryBSilva last edited by

Same here. I think its funny the devs didn't see this before shipping the update. And even so, it wasn't fixed yet...

[gonzalesl]

gonzalesl @leocg last edited by

@leocg Thank you. I think it would be beneficial for all of us if it was communicated at first place. Also to see a public roadmap

[ion-ursachi]

ion-ursachi last edited by

Opera One 114.0.5282.21, and still no fix? It's been a month already—what's the hold-up?

[metana]

metana last edited by

+1
Same here!

Opera One (version: 114.0.5282.21)
Update stream: Stable
System: Ubuntu Core 22 (x86_64; Ubuntu: GNOME)
Chromium version: 128.0.6613.162

[fernandoadms]

fernandoadms last edited by

same issue.

[HenryBSilva]

HenryBSilva last edited by

An update came out and its now working here.
Version: LVL 6 (core: 114.0.5282.84)

Thank you devs

[duviii]

duviii last edited by duviii

Updated to 114.0.5282.86 64bit on Windows 10 and still no change here, not fixed.

[Kartoffel-kartoffel]

Kartoffel-kartoffel @duviii last edited by

@duviii same, since it became a "Known" bug, three updates came out but still no fixes to this eye frying Problem.