Webengine_qt WLX Plugin - Dark theme support

[advice2020]

Linux/Debian 12 based

Hello,
I had mentioned about maybe adding dark theme support to the Webengine_qt WLX Plugin but at the time I do not think this feature was available.
I apologize, I cannot find the webpage at the moment to link, but I believe I came across a mentioning that the Webengine_qt added supported for Dark Themes in QT6.7
If this is correct, I was wondering in the future if you would consider adding this to your Webengine_qt WLX Plugin?
Unfortunately will not mean anything to me for a while because my Debian 12 based distro does not currently support QT6.7 but Arch based users would at least be able to use this for now, and hopefully someday I will as well :)
Thank You

Also thanks again for all the plugins you provide, they are very helpful

[j2969719]

as far as i understand, the dark theme will be enabled automatically if the content has support for dark themes, no?

only found the following options:

QWebEngineSettings::ForceDarkMode Specifies that all web contents will be rendered using a dark theme. For more information, see Auto dark theme. Disabled by default. (Added in Qt 6.7)

but tbh i think for local pages this will only add unnecessary issues with readability (eg there are some articles on my hdd that i saved around twenty years ago)

[advice2020]

@j2969719
Man every time I try to get you to join the dark side you deny my request.
How about this offer
j2969719.... Join me, and together, we can rule the.... gWLXy :)

I am not sure, would the plugin be able to detect that a dark theme is in use? and automatically apply it? That would be nice if it did, but maybe would cause issues as you mentioned for users who have older saved files?
If that was the case then there would be no way for user to turn this off, other than having to change there entire system back to lighter theme?

I tried using QT6 with DC a while back but seemed a little too soon for a Debian based system at the time.
Also the QT6 version of this WebEngine plugin did not work either at that time, hopefully it will the next time I try newer QT6 version.
I am planning in the future to try again with compiling a QT6 version now that they are more available in repo for Debian based distros.
But unfortunately even if I can get the WebEngine plugin to work in QT6, as mentioned I do not have access to version 6.7 yet in Debian.
You mentioned in past you are using Arch, do you by any chance have access to 6.7 where you could try enabling a dark theme, if you feel up to it. Or if any other users reading this use Arch/QT6.7 or newer maybe would be willing to give this a try?

If this does not automatically apply and that ForceDarkMode is required to achieve dark theme
I would not want to cause issues with your files saves from "A long time ago, in a galaxy far, far away...." but by any chance would it be possible / easy / something you would be willing to add within the script, where the user could/would have to enable this?
This way the default would not cause any issues, but user would be able to choose if want to try this setting out.

I apologize if any of this mentioned above does not make sense, I am not sure how themes are applied to newer / older pages.
Is it based on the page itself or the application the page is opened in? Older page versions saved would also be in an older versions of languages such as html. But if this could be added as an option at least user might be able to try it out to see if it works with their files.

Thank You

[j2969719]

its just that sloth is my spirit animal..

in case of qt 6.7+ uncommenting this line and running make qt6 will create a plugin with ForceDarkMode option hardcoded

tbh dont want to enable it by default because sometimes it looks meh (not to mention that it will be necessary to somehow determine whether qt darktheme is used)

as well as adding additional config routines only for the sake of one option for a certain versions of qt in a chromium-based plugin that ..well is not the fastest thing already

[advice2020]

:) sloth
Thank you for your response.
I was just kidding, of course.
Oh that is good to hear though that this could be added, thank you for doing this.
I agree I do not think I would make it the default either, but just nice that it is there if users want to give this feature a try.
As mentioned I unfortunately cannot test this at the moment because Debian does not have access to 6.7 yet, but in four years from now when it does, I will let you know how my tests go :)
Thank you again for making this update and again for all the plugins you provide for Linux in general.
I use these plugins a lot, I know you are not always happy with your work, but I think these plugins are great and have been very helpful, so thank you.