Closed Bug 1436027 Opened 7 years ago Closed 7 years ago

about:blank does not obey high-contrast color settings

Categories

(Core :: Layout, defect)

58 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1458956

People

(Reporter: k.kolev1985, Unassigned)

References

Details

(Keywords: dupeme)

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:58.0) Gecko/20100101 Firefox/58.0 Build ID: 20180128191252 Steps to reproduce: 1. From Windows 10 Settings -> Ease of Access -> Color & High-Contrast, choose the high-contrast black theme and click "Apply" there to apply it to the system. 2. Open Firefox. 3. Open Firefox settings -> General -> Colors and set Firefox to prefer the user's set colors over the colors set by the webpage author. That way Firefox will use the high-contrast's colors for the web content as well, and not just for its UI. 4. From the same dialog, make sure that "Use system colors" is not checked. I don't think that matters, but just to make sure. 5. Press OK in that dialog to apply and save the changes. 6. From the address bar of Firefox, open the "about:blank" page of the browser. Actual results: The loaded "about:blank" page is with a white background. Expected results: The loaded "about:blank" page should be with a black background.
Component: Untriaged → Theme
See Also: → 1438143
If this is only happening on the first tab, it's a duplicate of bug 1422507. If it happens in all tabs then this may be a new bug I wasn't aware of yet.
The bug occurs every time I load the page "about:blank". When opening a new tab, the loaded page is not "about:blank" and it is not affected by this bug.
See Also: → 1422507
See Also: → 1440865
This was fixed in Firefox 59, but seams to have being reintroduced in Firefox 60. Any thoughts?
Summary: The "about:blank: page does not obey high-contrast color settings → about:blank does not obey high-contrast color settings
Hi Everyone , i tried to reproduce this issue in build 58 Build ID: 20180128191252, 59, 60, latest version of nightly "62" and i can't reproduce it on a windows 10 x64, when i change the Windows Theme to a High Contrast Black, it seems that no matter what colors i choose in Firefox settings i will always get a black screen on "about:blank" page, as soon as i exit the high contrast theme my selected colors will be displayed in "about:blank". Here are the steps I used : 1. Set the Windows Theme to High Contrast Black. 2. Open FireFox > Options > General > Language and Appearance > Colors... 3. Changed the "Text" to "White" and the "Background" to "Red" 4. Set the "Override the Colors specified by the page with your selections above" to "Always" just to make sure that my colors are displayed. 5. Click OK and reach "about:blank" Actual Results : The Background image is always black , it will display the color i selected only after i exit the High Contrast Black theme. Please let me know if i'm missing any steps.
Flags: needinfo?(k_kolev1985)
In Firefox's color settings, my settings are set as so: - Text color: Black. - Background color: White. (those take effect only when a high-contrast theme is NOT in use on the system). - Use system colors: No. - Settings about links don't matter. - Prefer the set by you colors instead of the ones defined by the page: Only if a high-contrast theme is in use. With the settings set as so, each time I launch Firefox, the about:blank page loads with a white background, instead with a black one, as it should when the high-contrast black theme is active in Windows.
Flags: needinfo?(k_kolev1985)
Component: Theme → Layout
Product: Firefox → Core
Hi Everyone, Here are the results from the latest mozregression : INFO: Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=6e73121c7b6980bb182b541bf9e5915af6d78c00&tochange=b7efdfb3decd763c069c05b8e6398914de8a8396 This issue seems to be fixed in bug 1458956, hence IMO this is a dupe after the previously mentioned bug.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.