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
  1. This came up in some of the comments: https://github.com/whatwg/html/issues/11523#issuecomment-315... if you click the links instead of copy/pasting into your reader you get a page full of raw XML. It's not harmful or anything but it's not…
    comment by passivegains · 2025-08-20 · in "Remove mentions of XSLT from the html spec"
  2. …version numbers if there is no future and no past anyway?) https://whatwg.org/faq#living-standard https://github.com/whatwg/html/blob/main/FAQ.md#html-standar...
  3. …why removal would still hurt existing sites and applications, especially for embedded devices. https://github.com/whatwg/html/pull/11563#issuecomment-31970...
    comment by moritzwarhier · 2025-08-19 · in "Remove mentions of XSLT from the html spec"
  4. I think this post is useful where the thread author proposed some solutions to the people affected: https://github.com/whatwg/html/issues/11523#issuecomment-318... The main thing that seems unaddressed is the UX if a user opens a direct…
  5. Also, https://github.com/whatwg/html/issues/11523 (Should we remove XSLT from the web platform?) is not a request for community feedback. It's an issue open on the HTML spec for the HTML spec maintainers to consider. It was opened by a…
    comment by spankalee · 2025-08-19 · in "Remove mentions of XSLT from the html spec"
  6. …and it seems like they are trying to kill it before they have an open competitor in the web. https://github.com/whatwg/html/issues/11523
    comment by BoiledCabbage · 2025-08-19 · in "Remove mentions of XSLT from the html spec"
  7. …browser vendor is supportive and the issue was actually raised by Mozilla? See the agenda here: https://github.com/whatwg/html/issues/11131#issuecomment-274...
    comment by spankalee · 2025-08-19 · in "Remove mentions of XSLT from the html spec"
  8. A few things to note: - This isn't Chrome doing this unilaterally. https://github.com/whatwg/html/issues/11523 shows that representatives from every browser are supportive and there have been discussions about this in standards meetings:…
    comment by spankalee · 2025-08-19 · in "Remove mentions of XSLT from the html spec"
  9. WebKit's in favor: https://github.com/whatwg/html/issues/11523#issuecomment-314...
    comment by ameliaquining · 2025-08-19 · in "Remove mentions of XSLT from the html spec"
  10. …they opened to "gather community feedback" just three weeks ago. That one did get heated: https://github.com/whatwg/html/issues/11523 Google ignored everything, pushed on with the removal, and now pre-emptively closed this discussion, too
  11. Despite rather heated discussion just three weeks they started just two weeks prior https://github.com/whatwg/html/issues/11523
  12. …people who actually made the web happen (Smaug, Anne, Emilo, etc…) The vast majority of comments on https://github.com/whatwg/html/issues/11523 are polite and respectful. Also, "Smaug, Anne, Emilo" did not "make the web happen." They have…
  13. From the GitHub thread ( https://github.com/whatwg/html/issues/11523#issuecomment-315... ) > I don't think there's a strong "Open Web" argument to be made here. XML data files being able to be reformatted into HTML is somewhat of an…
  14. …pending an implementation. [1]: https://developer.chrome.com/blog/a-customizable-select [2]: https://github.com/whatwg/html/pull/10548
  15. We know why HTML alone can't do includes! In https://github.com/whatwg/html/issues/2791 the standards committee discussed this. The issue has been open for years. The first naysayer was @dominic: https://github.com/whatwg/html/issues/2791#i…
    comment by dfabulich · 2025-05-04 · in Why can't HTML alone do includes?
  16. …in a specific place of the document. HTML Imports could not do this without JavaScript. See https://github.com/whatwg/html/issues/2791#issuecomment-3112... for details.
    comment by uallo · 2025-05-03 · in Why can't HTML alone do includes?
  17. …(also mentioned in the comment section of the blog post): Client side include feature for HTML https://github.com/whatwg/html/issues/2791
    comment by uallo · 2025-05-03 · in Why can't HTML alone do includes?
  18. Native EventSource doesn’t let you set headers ([issue]( https://github.com/whatwg/html/issues/2177 )), so it’s harder to handle authentication.
    comment by rodorgas · 2025-04-12 · in You might not need WebSockets
  19. They do if you include <meta name="color-scheme" content="light dark"> Also see https://github.com/whatwg/html/issues/5426
  20. There's a new proposal to address this: https://github.com/whatwg/html/issues/5033
  21. It has been in the spec since 2009: https://github.com/whatwg/html/commit/0ed655652d52f0ab068fcb...
  22. …have analyzed impact of affected pages in the HTTP Archive dataset (about 12,000,000 pages), twice: https://github.com/whatwg/html/issues/7867#issuecomment-1977... https://github.com/whatwg/html/issues/7867#issuecomment-2595... The next…
  23. …JavaScript, but command/commandfor handles this and was recently added to the HTML specification: https://github.com/whatwg/html/pull/9841
  24. …was to add "max-height:stretch", "max-width:stretch". You can see the discussion for this here: https://github.com/whatwg/html/pull/5936#discussion_r5136422... The problem is that no browser had (and still has) shipped the "stretch"…
  25. Look at the actual commit. https://github.com/whatwg/html/commit/85effead0a5df3742ebe29... A document of this size will have typos, require clarification, get reorganized. It didn’t fundamentally change here.
  26. …I believe is the first to come out of it. https://developer.chrome.com/blog/rfc-customizable-select https://github.com/whatwg/html/issues/9799
  27. Doesn't appear to be. https://github.com/whatwg/html/pull/9841 https://github.com/whatwg/html/issues/9625 Seems to have been in the works since 2023, out in the open, with support from all major browser engines.
  28. …object. Targeting _new does not do this unless you explicity add the rel="noopener" yourself. https://github.com/whatwg/html/issues/4078 https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes...
  29. Agreed! There is a proposal for something like that in the WHATWG repo: https://github.com/whatwg/html/issues/8538
  30. …link text though; of all people Google employees should be cognizant of link accessibility). [0]: https://github.com/whatwg/html/issues/9799
    comment by matt_kantor · 2025-02-20 · in Customizable HTML Select
  31. …still called XHTML, it eventually retired the XHTML name due in part to confusion with XHTML 1 < https://github.com/whatwg/html/pull/2062 >. And so what we have instead is XML syntax for HTML (arguably also a tad misleading due to…
    comment by chrismorgan · 2025-02-08 · in HTML whitespace is broken (2024)
  32. …blockified - BFCs solve a separate, similarly hairy issue (floats & margin collapsing.)) [0]: https://github.com/whatwg/html/blob/main/FAQ.md#html-should-...
    comment by shiomiru · 2025-02-07 · in HTML whitespace is broken (2024)
  33. The issues were fixed actually. https://github.com/whatwg/html/wiki/dialog--initial-focus,-a... https://github.com/whatwg/html/pull/8199
    comment by chrishtr · 2024-12-06 · in <dialog>: The Dialog Element
  34. …that <dialog> should be removed from the platform because it's a bad API with multiple issues? https://github.com/whatwg/html/pull/4184#issuecomment-440405...
    comment by troupo · 2024-12-06 · in <dialog>: The Dialog Element
  35. …completely. Reason? No consensus on multiple issues relating to accessibility and security: https://github.com/whatwg/html/pull/4184#issuecomment-440405... And then boom! It was shipped everywhere with none of the issues discussed or…
    comment by troupo · 2024-12-06 · in <dialog>: The Dialog Element
  36. https://github.com/whatwg/html/issues/3577#issuecomment-2329... and the links inside appear to imply there's interest?
    comment by aragilar · 2024-10-29 · in Platform Strategy and Its Discontents
  37. …Do you have a draft spec available? Edit: Found a link to the Chrome blog which in turn links to https://github.com/whatwg/html/issues/9799 Initial question remains however, how are we to properly distinguish the user interface actions?
  38. …change! Jokes aside, you can participate in the discussion yourself here: https://github.com/whatwg/html/issues/10520 But be warned, you will probably not be able to convince people with just "Please, just no!". > I get the sense th
  39. …but the work is a bit stalled. https://www.stefanjudis.com/today-i-learned/safari-allows-to... https://github.com/whatwg/html/issues/3518 Another cool feature Apple spearheaded was the ability for websites to indicate the change password…
  40. …no one else picked up, so it was removed. Now it’s the last mover. https://caniuse.com/style-scoped https://github.com/whatwg/html/issues/552
    comment by oefrha · 2024-10-14 · in Inline Scope for CSS
  41. …addresses as a binary format. You aren't even allowed to do NFC / NFD / NFKC etc normalization. https://github.com/whatwg/html/issues/4562#issuecomment-2096... Unicode has some standards which are slightly better, but they're only for…
  42. The only way to get out of the current front end hell IMO is if we get client side import: https://github.com/whatwg/html/issues/2791
    comment by candiddevmike · 2024-09-29 · in Web components are okay
  43. There's this HTML spec issue for an include feature that I think could always use more support: https://github.com/whatwg/html/issues/2791 One of the things said in there is that they look for usage of userland solutions. I mentioned in…
    comment by spankalee · 2024-07-29 · in SVG Triangle of Compromise
  44. …to CommamdFor/InvikerAction work that's been chunking along. https://github.com/github/catalyst https://github.com/whatwg/html/issues/9625#issuecomment-2115... )
  45. …that quirky UI library's dialog. [1] https://developer.chrome.com/blog/what-is-the-top-layer [2] https://github.com/whatwg/html/issues/8339 [3] https://developer.chrome.com/blog/entry-exit-animations [4]…
    comment by dialogawesome · 2024-05-17 · in Popover API
  46. …there was interest of all major browser manufactors to implement ruby standard properly. [1] https://github.com/whatwg/html/pull/6478
  47. HTML switch was already requested in 2018: https://github.com/whatwg/html/issues/4180
    comment by wubin · 2024-03-05 · in An HTML Switch Control
  48. …DOM too now! There's a long-standing WHATWG feature request open for client-side includes here: https://github.com/whatwg/html/issues/2791 And several userland custom element implementation, like https://www.npmjs.com/package//html-include-…
  49. https://github.com/whatwg/html/pull/9546
    comment by halostatue · 2024-02-29 · in An HTML Switch Control
  50. https://github.com/whatwg/html/pull/9546
    comment by halostatue · 2024-02-29 · in An HTML Switch Control