News for hackers. Stuff that matters.

A comment on Show HN: Using Google AMP to build a Medium-style Jekyll site that loads in 65ms. Parent comment

Re:Show HN: Using Google AMP to build a Medium-style Jekyll ... by sillysaurus3 on Tuesday March 15, 2016 @02:43AM (#11287912)
All browsers I've tried seem to render it fine and quickly (assuming js and the normal bells and whistles).

That says a lot about HTML validation, then.

[ Parent | on HN ]
Re:Show HN: Using Google AMP to build a Medium-style Jekyll ... by robotresearcher on Tuesday March 15, 2016 @02:54AM (#11287958)
Or perhaps about the remarkable robustness of renderers faced with non-compliant markup.

Thanks, WebKit (etc) authors! You worked hard so others don't have to.

[ Parent | on HN ]
Re:Show HN: Using Google AMP to build a Medium-style Jekyll ... by magicalist on Tuesday March 15, 2016 @03:04AM (#11287981)
s/WebKit/WHATWG
[ Parent | on HN ]
Re:Show HN: Using Google AMP to build a Medium-style Jekyll ... by currysausage on Tuesday March 15, 2016 @06:22AM (#11288623)
Not sure why you're being downvoted. WebKit actually implements the WHATWG HTML parsing algorithm [1], and so do Trident [2] and Gecko [3].

The W3C HTML 4 spec didn't waste a word on parsing and simply referred to SGML [4], which (for very good reasons) no relevant browser actually implemented. Obviously, browser developers did some crazy/remarkable things before the WHATWG came along, but a lot of credit for today's lenient HTML parsing certainly belongs with the WHATWG.

[1] https://webkit.org/blog/1273/the-html5-parsing-algorithm/

[2] https://blogs.msdn.microsoft.com/ie/2011/07/06/html5-parsing...

[3] https://hacks.mozilla.org/2010/05/firefox-4-the-html5-parser...

[4] https://www.w3.org/TR/html4/conform.html#h-4.2

[ Parent | on HN ]