-
Notifications
You must be signed in to change notification settings - Fork 15
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
dark mode #56
Comments
@jimmywarting thanks for raising this issue. This spec is authored with ReSpec.js and that tool is currently lacking dark mode support. You can voice your support for this feature in https://github.com/w3c/respec/issues/2651 (or even submit a PR to implement this feature in that tool). Some specs are authored with another tool, Bikeshed, that does have dark mode support, so you may see some other specs go dark. Once implemented this spec will automatically "go dark" (no pun intended), so I'm closing this issue with an expectation you'll track the feature development through the mentioned issue. While you're here, please feel free to check out https://github.com/w3c/battery/blob/gh-pages/energy-saver-mode-explainer.md that was initiated based on your proposal and submit any feedback via #9. We appreciate your continued contributions in this space. |
Looks grate! some nit pick, while reading this code example: let b = await navigator.getBattery();
if (b.energySaverMode) {
saveEnergy();
}
b.energysavermodechange = () => {
if (this.energySaverMode) saveEnergy();
} I could not help but thinking: Hmm is I don't know how i feel about the I like android / MacOS / iOS naming convention better.
It's a clear indication that it's a boolean. an alternative name could be also this code example: - b.energysavermodechange = () => {
+ battery.onenergysavermodechange = () => {
if (this.energySaverMode) saveEnergy();
} |
Thanks for this great feedback, but please move it to #9 so it is in the right place 😀 |
Could you add a dark theme to https://www.w3.org/TR/battery-status?
it's currently very bright
The text was updated successfully, but these errors were encountered: