Blank page is white in Nightly 69.0a1 (2019-06-26) under Mac OS dark mode (about:blank)
Categories
(Firefox :: Theme, defect, P3)
Tracking
()
People
(Reporter: pshirshov, Unassigned)
Details
Attachments
(1 file)
3.09 MB,
video/quicktime
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.102 Safari/537.36 Vivaldi/2.6.1566.44
Steps to reproduce:
- Install Nightly with clean profile on Mac OS
- Turn on Dark Mode
- Run Nightly
- Navigate to about:blank
Actual results:
White page opened
Expected results:
Blank page background must respect Dark Mode - it's physically painful when it happens at night.
If I change browser.display.background_color - it helps. Though I'm sure that the browser must consider Dark Mode for about:blank without user intervention.
Also it's somehow related to https://bugzilla.mozilla.org/show_bug.cgi?id=1422507 but that one seems to be fixed.
Comment 2•5 years ago
|
||
I can reproduce this on Firefox Nightly 69.0.1(2019-07-01) with macOS 10.15 Beta (19A487m).
Comment 3•5 years ago
|
||
Reproducible also on Firefox Release 67.0.4 version, Mac OS X 10.15.
I also tested on Mac OS X 10.14 and the issue is reproducible, I don't think this bug is related with the new 10.15 Mac OS version.
Updated•5 years ago
|
Comment 4•5 years ago
|
||
This really hurts your eyes regularly, especially if you have configured Firefox to show a blank page for new tabs and windows while
using the recommended addon Dark Reader https://addons.mozilla.org/de/firefox/addon/darkreader/ or similar.
Comment 6•5 years ago
|
||
What would be the right place to fix this? Could you move this bug into the appropriate component?
Comment 7•5 years ago
|
||
I don't know how web-compatible it would be to do this for all about:blank pages (I imagine: not very.). It would be OK for pages that the user opens themselves which are not related to the ones opened by the web. I don't know whether/how we'd distinguish those, and/or how we'd make dark mode affect them. We'd also need to be cautious about how this interacts with browser.display.background_color
. :ntim, do you have ideas?
(I'm removing release tracking flags because this isn't a release-specific problem, it's always worked like this.)
Comment 8•5 years ago
|
||
:bz mentioned why this change can be problematic: https://phabricator.services.mozilla.com/D30013#887146
Description
•