HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
whatwg
html
HTML2015–2026
whatwg / html

html

HTML Standard

Web Development
Explore on GitHubRead Hacker News discussions
149Distinct people
217Mentions
1Explicit recommenders
9.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

HTML Standard

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I tried to leave some details here on the situation downthread: https://news.ycombinator.com/item?id=12849375 As for actual technical differences, the vast majority of them are…

domenicd used a recommendation phrase. One indexed comment matches. 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

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM 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 year217 dated mentions

Observed mentions: 2015-08-27 22:16:26 UTC to 2026-10-17 23:55:29 UTC.

0204060802015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 7 mentions; 3 submissions, 4 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 10 mentions; 0 submissions, 10 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 9 mentions; 2 submissions, 7 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 10 mentions; 2 submissions, 8 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 27 mentions; 0 submissions, 27 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 19 mentions; 3 submissions, 16 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 14 mentions; 4 submissions, 10 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 24 mentions; 1 submissions, 23 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 80 mentions; 8 submissions, 72 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 11 mentions; 1 submissions, 10 comments. Incomplete calendar period.2026*

* 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
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC110
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC734
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC10010
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC505
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC927
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC1028
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC27027
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC19316
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC14410
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC24123
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC80872
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC11110

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
This repository hosts the HTML Standard. Code of conduct We are committed to providing a friendly, safe and welcoming environment for all. Please read and respect the WHATWG Code of Conduct. Contribution opportunities We appreciate all contributions, see the guidelines for contributing for details, including information on how to build HTML output from the source file so you can preview your changes locally. Tests Tests are in the html/ directory of the web-platform-tests repository. Blame As the source file is too large for GitHub's blame utility, use blame for source on searchfox instead.
Read the full README on GitHub

What Hacker News says

217 sources
em-bee·Oct 17, 2026
XSLT RIP(https://xslt.rip/) 698 points|edent|11 months ago|464 comments https://news.ycombinator.com/item?id=45873434 Removing XSLT for a more secure browser(https://developer.chrome.com/docs/web-platform/deprecating-x...) 183 points|justin-reeves|1 year ago|337 comments https://news.ycombinator.com/item?id=45823059 Intent to Deprecate and Remove XSLT(https://groups.google.com/a/chromium.org/g/blink-dev/c/CxL4g...) 87 points|CharlesW|1 year ago|149 comments https://news.ycombinator.com/item?id=45779261 A look at XSLT 3.0 (2017)(https://www.xml.com/articles/2017/02/14/why-you-should-be-us...) 75 points|protomolecool|1 year ago|45 comments https://news.ycombinator.com/item?id=45026013 Show HN: I Built a XSLT Blog Framework(https://vgr.land/content/posts/20250821.xml) 116 points|vgr-land|1 year ago|68 comments https://news.ycombinator.com/it
Read the rest
em?id=45006098 Show HN: JavaScript-free (X)HTML Includes(https://github.com/Evidlo/xsl-website) 211 points|Evidlo|1 year ago|114 comments https://news.ycombinator.com/item?id=44988271 Should the web platform adopt XSLT 3.0?(https://github.com/whatwg/html/issues/11578) 133 points|protomolecool|1 year ago|108 comments https://news.ycombinator.com/item?id=44987552 XSLT removal will break multiple government and regulatory sites(https://github.com/whatwg/html/issues/11582) 160 points|colejohnson66|1 year ago|146 comments https://news.ycombinator.com/item?id=44987346 Google did not unilaterally decide to kill XSLT(https://meyerweb.com/eric/thoughts/2025/08/22/no-google-did-...) 103 points|bkardell|1 year ago|128 comments https://news.ycombinator.com/item?id=44987239 "Remove mentions of XSLT from the html spec"(https://github.com/whatwg/html/pull/11563) 388 points|troupo|1 year ago|535 comments https://news.ycombinator.com/item?id=44952185 Should we remove XSLT from the web platform?(https://github.com/whatwg/html/issues/11523) 73 points|edent|1 year ago|96 comments https://news.ycombinator.com/item?id=44909599 XSLT: A Precision Tool for the Future of Structured Transformation(https://www.xml.com/articles/2025/07/19/xslt-precision-tool-...) 58 points|protomolecool|1 year ago|59 comments https://news.ycombinator.com/item?id=44633384 XSLT – Native, zero-config build system for the Web(https://github.com/pacocoursey/xslt) 392 points|_kush|1 year ago|325 comments https://news.ycombinator.com/item?id=44393817 Intent to Unship: XSLT(https://groups.google.com/a/mozilla.org/g/dev-platform/c/ZRy...) 5 points|tambourine_man|2 months ago|1 comments (this list is incomplete. but we just had a power outage (including getting zapped, so i am submitting this now to not lose it)
In Chrome and Edge are removing XSLT: what breaks and what does not
csande17·May 24, 2026
As far as I can tell, this is not actually allowed by the current proposal. The definition of the "find markers" algorithm in https://github.com/whatwg/html/pull/11818 requires that the <?end> marker be a sibling of the <?start> marker in the DOM, so they can't have different parents like this. Well, you're allowed to write it, but the browser will just ignore the <?end> marker. The range will end at the </em> tag, the same place https://github.com/WICG/declarative-partial-updates/blob/mai... says it goes by default if you don't write the <?end> at all. (That default wouldn't make a ton of sense if patch ranges were allowed to break out of their parent elements like this.) Jake Archibald thinks it'd be cool to use a similar syntax to do CSS highlights, but there are other problems with that (like not being able to create overlapping range
Read the rest
s), and he's not on the Chrome team that's pushing this proposal.
In API proposed by Chrome: Declarative partial updates
afavour·May 20, 2026
> aren't we supposed to reject these technologies that allow Google to Embrace, Extend, Extinguish In what way is this technology a means to embrace, extend and extinguish? This seems like a logical extension of existing web APIs. If we reject everything out of hand then the platform won't improve. It's going through the standards process: https://github.com/whatwg/html/issues/10650
In HTML-in-Canvas Demos
adzm·Apr 13, 2026
This is the right move. https://github.com/whatwg/html/issues/11724#issuecomment-419... and adding a feature to browsers to explicitly use the info is the best solution really. The problem is that there was a change without a backup solution without making a native app, but preventing people from accidentally uploading their location in an image is the right move. It really needs to be more well known and handled automatically.
In Android now stops you sharing your location in photos
troupo·Nov 17, 2025
> What, to you, would constitute sufficient proof? Is it feasible to gather the evidence your suggestion would require? Let me quote from my comment, again: --- start quote --- The guy pushing "intent to deprecate" didn't even know about the most popular current usage (displaying podcast RSS feeds) until after posting the issue and until after people started posting examples --- end quote --- I would like to see more evidence than "we couldn't care less, remove it" before a consensus on removal, before an "intent to deprecate" and before opening a PR to Chrome removing the feature. Funnily enough, even the "browser consensus" looks like this: "WebKit is cautiously supportive. We'd probably wait for one implementation to fully remove support": https://github.com/whatwg/html/issues/11523#issuecomment-314... BTW. Literally the only "evidence
Read the rest
" originally presented was "nearly 100% of sites use JS, while 1/10000 of those use XSLT.": https://github.com/whatwg/html/issues/11523#issuecomment-315... which was immediately called into question: https://github.com/whatwg/html/issues/11523#issuecomment-315... and https://github.com/whatwg/html/issues/11523#issuecomment-315... and that's before we account for google's own docs saying they have a blind spot in the enterprise/corporate setting where people suspect the usage may be higher. Also, as I say. I think the main issue isn't XSLT itself. XSLT is a symptom.
In Google is killing the open web, part 2

Showing the 15 most recent of 217 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.