Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prevent white flashes when Firedragon loads new pages #68

Open
ShalokShalom opened this issue Oct 2, 2023 · 3 comments
Open

Prevent white flashes when Firedragon loads new pages #68

ShalokShalom opened this issue Oct 2, 2023 · 3 comments
Labels
enhancement New feature or request

Comments

@ShalokShalom
Copy link

Hi there 👍🏻

I deeply appreciate that Garuda comes with Darkreader by default.
One thing, that this does not solve, is the bleak white loading screen, that loads up, before Darkreader can kick in.

This is a Firefox thing, not specific to the webpage.
I remember having an issue open on that for years, but they dont care.
Could we change that in the ChromeCSS: https://support.mozilla.org/en-US/questions/1269392

Or something like that.

@dr460nf1r3
Copy link
Owner

That is a great idea. One doubt - if we provide this by default, would everyone who opts out of DarkReader be "handicapped" by that?

@charset "utf-8";
/* CSS Document */

@-moz-document url("about:newtab") {
body { background-color: #011326 !important;}
}

@-moz-document url(chrome://browser/content/browser.xul) {
browser[type="content-primary"] {background: #011326 !important}
}

We would have to test how it looks without Dark Reader active.

@dr460nf1r3 dr460nf1r3 added the enhancement New feature or request label Oct 2, 2023
@ShalokShalom
Copy link
Author

Well, that's the case. A white background adds nothing of value. Even without Darkreader, the only "downside" of this is, that you can't be blinded.

Imho, that should be default in Firefox for decades. 🙄

@ShalokShalom
Copy link
Author

ShalokShalom commented Oct 27, 2023

This is currently prevented from working all the time by a regression introduced with 115. This will be fixed in the next release.

I suggest shipping this configuration with 120.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants