More details on supports-color-schemes: https://github.com/w3c/csswg-drafts/issues/3299
Web inspector also has a widget that toggles between light and dark mode.
In Release Notes for Safari Technology Preview 71w3c
csswg-drafts
Bikeshed2016–2026
w3c / csswg-drafts
csswg-drafts
CSS Working Group Editor Drafts
87Distinct people
121Mentions
3Explicit recommenders
4.9KGitHub stars
What to know before exploring
What it is
CSS Working Group Editor Drafts
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
Huh (having scanned but not read in detail the post), interesting approach. I'm not that well-versed in this area (as a game developer, I tend to jump straight to…
jan_Inkepa used a recommendation phrase. 3 indexed comments match. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 2:59:53 AM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year121 dated mentions
Observed mentions: 2016-09-21 13:16:42 UTC to 2026-10-08 18:33:14 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 8 | 2 | 6 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 6 | 2 | 4 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 8 | 1 | 7 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 13 | 3 | 10 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 10 | 1 | 9 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 19 | 3 | 16 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 20 | 3 | 17 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 10 | 0 | 10 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 15 | 0 | 15 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 11 | 2 | 9 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
Types of Workflows
workflows/build-specs.yml - builds the entire repository of Editor's Drafts, along with a summary page. Also builds any .issues Issues-List files, and Markdown files. Deploys all the results to the repo's gh-pages
workflows/SPEC-NAME-1.yml - each of these auto-publish one spec in the repo. Do not modify them by hand; they are auto-generated by generate-auto-publish-workflows.py and auto-publish-template.yml. Instead, update and run this .py file and commit the results.
Read the full README on GitHubWhat Hacker News says
6 sourcesThe CSS WG earlier this year resolved to take on a spec defining this, and there's implementer interest, so it's highly likely to happen.
(This is https://github.com/w3c/csswg-drafts/issues/2701 .)
In Incomplete List of Mistakes in the Design of CSSApple is proposing a new CSS color-filter property [1], which would do the same thing as Mail does for its content. Actually, Apple is already using color-filter internally in the Mail app.
Safari allows setting user style sheets in its Preferences: Advanced > Style sheet, so one could perhaps add a user style sheet with color-filter.
[1] https://github.com/w3c/csswg-drafts/issues/2875
In Using Dark Mode in CSS with MacOS MojaveDark Mode in CSS – w3c/csswg-drafts
3 points · Open discussionSome of Chrome's decisions are definitely IE-like.
For example, the FF team felt that flex/grid should become the new layout standard, and deprecated or accidental behaviors of the past could be sunset by doing it right on Flex/Grid. So, for example, margin-top: 10% would be percent of height instead of percent of width when on a flexbox or grid item.[1]
Chrome did it their way and wouldn't discuss the issue, and eventually FF caved because Chrome has a near-monopoly.
This idea of implementing bad design and forcing it on the world, won't end well for the user.
Not to mention the whole recent hullaboo about hiding the www / m / whatever prefixes.
[1] https://github.com/w3c/csswg-drafts/issues/2085
[2] https://news.ycombinator.com/item?id=17927972
In Am I logged in or not? GDPR case study on the example of Chrome browser changeProposal for :event:then(:event) selector
1 points · Open discussion