Hacker GitHub

← All repos

whatwg/html

View on GitHub ↗ ★ 9,433 HTML

HTML Standard

218 mentions on Hacker News by 149 people: 25 stories, 193 comments · first 2015-08-27 · latest 2026-10-17

Mentions per year 218 mentions · busiest year 2025 (80)
20082026
AllStoriesComments NewestTopOldest
  1. …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…
    comment by em-bee · 2026-10-17 · in Chrome and Edge are removing XSLT: what breaks and what does not
  2. There's a long discussion about XSLT removal here: https://github.com/whatwg/html/issues/11578#issuecomment-595... (the link is to the comment with this proposal https://github.com/doriantaylor/swet which already is much better than any…
    comment by troupo · 2026-10-17 · in Chrome and Edge are removing XSLT: what breaks and what does not
  3. …need put more effort into the "legacy" XMLHttpRequest, WebSocket, and EventSource networking APIs. https://github.com/whatwg/html/issues/2177#issuecomment-2672...
    comment by htunnicliff · 2026-09-12 · in WebSocket is a legacy API (2016)
  4. ▲ 2
    WebSocket is a legacy API (2016)
    story by htunnicliff · 2026-09-12 · 1 comment
  5. …using it) would avoid the need for CORS preflight requests. There is a separate issue for QUERY: https://github.com/whatwg/html/issues/12594
    comment by CodesInChaos · 2026-06-17 · in RFC 10008: The new HTTP Query Method
  6. See https://github.com/whatwg/html/issues/12594 .
    comment by chrismorgan · 2026-06-17 · in RFC 10008: The new HTTP Query Method
  7. …been my dream for decades. There's a WHATWG proposal to do just that if you want to add your voice: https://github.com/whatwg/html/pull/11347
    comment by acabal · 2026-06-17 · in RFC 10008: The new HTTP Query Method
  8. …(I didn't check when this happened in Chromium) Related WHATWG discussion: https://github.com/whatwg/html/issues/3099
    comment by rzzzt · 2026-06-14 · in Show HN: Kage – Shadow any website to a single binary for offline viewing
  9. …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…
    comment by csande17 · 2026-05-24 · in API proposed by Chrome: Declarative partial updates
  10. …everything out of hand then the platform won't improve. It's going through the standards process: https://github.com/whatwg/html/issues/10650
    comment by afavour · 2026-05-20 · in HTML-in-Canvas Demos
  11. 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…
    comment by adzm · 2026-04-13 · in Android now stops you sharing your location in photos
  12. HTML 5 still gets new features all the time: https://github.com/whatwg/html But they'll never add new standard tags with hyphens.
    comment by reddalo · 2025-12-29 · in You can make up HTML tags
  13. …my modal components with the <dialog> element, but had to reverse everything due to this issue: https://github.com/whatwg/html/issues/9936 In short: you can’t have an interactive popover (e.g. a toast notification) on top of a dialog…
    comment by hn111 · 2025-12-28 · in Replacing JavaScript with Just HTML
  14. ▲ 2
    We should just change the spec and ask Firefox to change
    story by ColinWright · 2025-12-17 · 1 comment
  15. …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" originally presented was "nearly 100% of sites…
    comment by troupo · 2025-11-17 · in Google is killing the open web, part 2
  16. …much less on board though[1][2], enough that Google referenced that in their announcement. [1] https://github.com/whatwg/html/issues/11578 [2] https://github.com/whatwg/html/issues/11523
    comment by _heimdall · 2025-11-17 · in Google is killing the open web, part 2
  17. …podcast RSS feeds) until after posting the issue and until after people started posting examples: https://github.com/whatwg/html/issues/11523#issuecomment-315... Meanwhile Google's own document says that's not how you approach deprecation:…
    comment by troupo · 2025-11-17 · in Google is killing the open web, part 2
  18. …at this point…) On this, I think, we should have some kind of AI-generated meta-tag, like this: https://github.com/whatwg/html/issues/9479
    comment by vissi · 2025-11-11 · in AI documentation you can talk to, for every repo
  19. …by killing it Google can control the media. XSLT is used worldwide by [multiple government sites]( https://github.com/whatwg/html/issues/11582 ). Google are now trying to control LEGISLATION. With these technologies removed what is…
    comment by neilv · 2025-11-10 · in XSLT RIP
  20. …by podcasts until after people flooded the issue with examples and requests not to remove. E.g. https://github.com/whatwg/html/issues/11523#issuecomment-315... [1] Reaction was "cautiously agree" btw. In that same issue,…
    comment by troupo · 2025-11-10 · in XSLT RIP
  21. …have enough time/interest to bother with it. [0]: https://github.com/mfreed7/xslt_extension [1]: https://github.com/whatwg/html/issues/11523#issuecomment-315... [2]: https://gitlab.gnome.org/World/Rust/markup-rs/xrust
    comment by gucci-on-fleek · 2025-11-10 · in XSLT RIP
  22. …://www.maxchernoff.ca/tools/Stardew-Valley-Item-Finder/ [1]: https://www.maxchernoff.ca/atom.xml [2]: https://github.com/whatwg/html/pull/11563#issuecomment-31909... [3]: https://github.com/gucci-on-fleek/lua-widow-control/blob/852...
    comment by gucci-on-fleek · 2025-11-10 · in XSLT RIP
  23. https://github.com/whatwg/html/issues/11146#issuecomment-275... panos: next item, removing XSLT. There are usage numbers. stephen: I have concerns. I kept this up to date historically for Chromium, and I don't trust the use counters based…
    comment by thro1 · 2025-11-09 · in Removing XSLT for a more secure browser
  24. https://github.com/whatwg/html/issues/11523 From there they link to the minutes for the meeting where this was raised. Interestingly the Google engineer who raised this at the meeting was formerly at Mozilla for years. I don’t know if…
    comment by dpark · 2025-11-07 · in Removing XSLT for a more secure browser
  25. …the WHATNOT meeting notes linked to from that GH Issue... though I have no idea who smaug is. [0] < https://github.com/whatwg/html/issues/11523 > [1] < https://github.com/whatwg/html/issues/11146#issuecomment-275... >
    comment by simoncion · 2025-11-05 · in Removing XSLT for a more secure browser
  26. …list of origins that participate in a reverse origin trial we could perhaps participate sooner. — https://github.com/whatwg/html/issues/11523#issuecomment-314... Describing either of those as “they preferred to keep it” is blatantly untrue.
    comment by JimDabell · 2025-11-05 · in Removing XSLT for a more secure browser
  27. …their browser engines. [^0]: https://github.com/mozilla/standards-positions/issues/1287#i... [^1]: https://github.com/whatwg/html/issues/11523#issuecomment-314...
    comment by sangeeth96 · 2025-11-05 · in Removing XSLT for a more secure browser
  28. …https://andrewstiefel.com/style-atom-xsl/ Looks like it's been raised on the whatwg issue too: https://github.com/whatwg/html/issues/11523#issuecomment-315...
    comment by mbo · 2025-11-01 · in Intent to Deprecate and Remove XSLT
  29. …WebKit and Chromium integrate with libxslt in a way that's inherently bad for performance ( https://github.com/whatwg/html/issues/11578#issuecomment-321 ... ) Just Firefox XSLT is faster, better, cheaper than Google's (and JS), same, old…
    comment by thro1 · 2025-11-01 · in Intent to Deprecate and Remove XSLT
  30. …to build a custom time field I asked the HTML spec editors to fix this, but thus far they haven’t: https://github.com/whatwg/html/issues/6698
    comment by skissane · 2025-10-27 · in Avoid 2:00 and 3:00 am cron jobs (2013)
  31. …and Safari re-introduced them in 2022. The was a proposal to remove the spec entirely in 2015: https://github.com/whatwg/html/issues/315 I don't think I've seen a feature that was shipped in s browser for years, then removed, and then…
    comment by troupo · 2025-10-17 · in A conspiracy to kill IE6 (2019)
  32. …from it. Though as I understand it it's possible that this might not be the case for much longer: https://github.com/whatwg/html/issues/11523
    comment by rimunroe · 2025-10-08 · in Git, JSON and Markdown walk into bar
  33. Related discussion to remove XSLT from the web platform: https://github.com/whatwg/html/issues/11523
    comment by Pfeil · 2025-09-20 · in Feedmaker: URL + CSS selectors = RSS feed
  34. ▲ 2
    Client side include feature for HTML
    story by jollyjerry · 2025-09-19 · 2 comments
  35. …section, it reminded me of this issue to push for first-class includes in web platform https://github.com/whatwg/html/issues/2791
    comment by jollyjerry · 2025-09-19 · in No CSS, No JavaScript. Longevity on the Web
  36. There is a related issue to instead add XSLT 3 support [1] [1] https://github.com/whatwg/html/issues/11578
    comment by _heimdall · 2025-08-25 · in Show HN: I Built a XSLT Blog Framework
  37. …a shame these Discussions got so heated, but that's just the nature of the internet, I guess. [1]: https://github.com/whatwg/html/issues/11523#issuecomment-318... //Edit: Rephrased "PRs" to "Discussions".
    comment by MrGilbert · 2025-08-25 · in Show HN: I Built a XSLT Blog Framework
  38. …can't say this out loud, so they instead have @mfreed7 cherry-pick some numbers as justification. ( https://github.com/whatwg/html/issues/11582#issuecomment-321... ) Mason Freed (mfreed7), XSLT, 2025, Jorge Villalobos, ' legacy ' Firefox…
    comment by thro1 · 2025-08-23 · in XSLT removal will break multiple government and regulatory sites
  39. …WebKit and Chromium integrate with libxslt in a way that's inherently bad for performance ( https://github.com/whatwg/html/issues/11578#issuecomment-321... ) Just Firefox XSLT is faster, better, cheaper than Google's (and JS), same, old…
    comment by thro1 · 2025-08-23 · in Should the web platform adopt XSLT 3.0?
  40. …effects of removal. It's hard to tell what will break without being able to turn it off and see. https://github.com/whatwg/html/issues/11582#issuecomment-320... --- end quote ---
    comment by troupo · 2025-08-23 · in Show HN: JavaScript-free (X)HTML Includes
  41. …WebKit and Chromium integrate with libxslt in a way that's inherently bad for performance ( https://github.com/whatwg/html/issues/11578#issuecomment-321... ) Just Firefox XSLT is faster, better than Google's (and JS), same, old Firefox…
    comment by thro1 · 2025-08-23 · in Google did not unilaterally decide to kill XSLT
  42. …a pin in it, and talk with olli next time? panos: next thing is file upload control rendering [0] https://github.com/whatwg/html/issues/11146#issuecomment-275...
    comment by shakna · 2025-08-23 · in Show HN: JavaScript-free (X)HTML Includes
  43. …too – maybe I’ll get to it finally this time; definitely if XSLT 3.0 gets into web standards: https://github.com/whatwg/html/issues/11578 , https://news.ycombinator.com/item?id=44987552 Also, I’ve put together a simple XSLT playgroung a…
    comment by notpushkin · 2025-08-22 · in Show HN: JavaScript-free (X)HTML Includes
  44. …will be gated behind a flag. Google have also asked for it to be removed from the standard [0]. [0] https://github.com/WHATWG/html/issues/11523
    comment by shakna · 2025-08-22 · in Show HN: JavaScript-free (X)HTML Includes
  45. Brian's comment here is really important for bystanders to be able to understand the process: https://github.com/whatwg/html/issues/11582#issuecomment-320... Removals sometimes take a decade or more, or sometimes don't happen at all. Just…
    comment by spankalee · 2025-08-22 · in XSLT removal will break multiple government and regulatory sites
  46. …the proposal) is not the one who came up with the 357 number; that was zcorpan of Mozilla ( https://github.com/whatwg/html/issues/11523#issuecomment-320... ), so mfreed7 is talking about the list they got from zcorpan.
    comment by Arnavion · 2025-08-22 · in XSLT removal will break multiple government and regulatory sites
  47. This is a fair response to the point: https://github.com/whatwg/html/issues/11582#issuecomment-321... Frankly I think this is a tempest in a teapot, and the primary reason people are complaining is because Google is sponsoring the idea,…
    comment by otterley · 2025-08-22 · in XSLT removal will break multiple government and regulatory sites
  48. ▲ 133
    Should the web platform adopt XSLT 3.0?
    story by protomolecool · 2025-08-22 · 108 comments
  49. ▲ 160
    XSLT removal will break multiple government and regulatory sites
    story by colejohnson66 · 2025-08-22 · 146 comments
  50. …do the work. The proposal suggests the browsers wholesale remove support and forget about it. https://github.com/whatwg/html/issues/11523#issuecomment-315...
    comment by colejohnson66 · 2025-08-21 · in "Remove mentions of XSLT from the html spec"