report(redesign): respect prefers-color-scheme

[connorjclark]

You can test this in FF 67 beta. Just need to change OS to dark mode (for osx, Appearance -> Dark)

[brendankenny]

force true incase already dark (ex: scores all 100)

really report-ui-features.js should be setting dark mode for fireworks anyways, not report-renderer.js. Not everything that runs the report renderer is showing only the report (PSI, web.dev), so it shouldn't be reaching out and adding classes to body anyways.

Can you move it in here? Not sure what's the best way to do it...e.g check for `.score100', maybe?

[connorjclark]

done. can I remove the check for devtools too?

[googlebot]

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

ℹ️ Googlers: Go here for more info.

[paulirish]

failing on travis

[connorjclark]

@paulirish fixed

[paulirish]

@hoten your merge added back the test that was removed https://github.com/GoogleChrome/lighthouse/pull/8842/files#diff-219d90e30aff619017455031ea860fec

[patrickhulce]

LGTM!

what's up with travis though, a push 2 hours ago and still pending?

[connorjclark]

FYI Chrome 76 will support prefers-color-scheme.