July 6th, 2024

HTML5 Differences from HTML4 (2014)

The W3C Working Group's "HTML5 Differences from HTML4" document outlines changes in syntax, elements, APIs, and compatibility. HTML5 introduces new elements, MathML, SVG support, and emphasizes backward compatibility for modern web development.

Read original articleLink Icon
HTML5 Differences from HTML4 (2014)

The "HTML5 Differences from HTML4" document by the W3C Working Group describes the variances between the HTML5 and HTML4 specifications. It covers changes in syntax, language elements, APIs, and backward compatibility considerations. The HTML5 specification aims to provide a single language for both HTML and XML syntax, with detailed processing models to enhance interoperability. Notable changes include the introduction of new elements like section, article, main, and aside for improved document structure. Additionally, HTML5 allows MathML and SVG elements within documents, provides detailed rules for character encoding declaration, and specifies the use of doctype for standards mode rendering. The document emphasizes backward compatibility with older elements and attributes, ensuring support by user agents. Overall, HTML5 represents a significant evolution from HTML4, addressing modern web development needs and enhancing markup for various types of content.

Link Icon 6 comments
By @deaddodo - 5 months
Whenever I see these old W3C docs mentioning old standards (MathML, in this case), it reminds me of how short-lived and little supported VRML was in browsers.

I remember a scant few months were it would run in maybe Netscape? And then there were a couple years it was supported via Java Applets before being completely phased away. At least, in the web space; maybe it found purchase elsewhere.

By @bruce511 - 5 months
I still come across people using the term HTML5 as if it's "a thing". For example "our system has been updated to HTML5".

Whereas HTML5 spans more than a decade of continuous browser improvement and extension. It is an "era" or "mindset" not a "specification".

HTML5 was a way of discarding the mindset of "versioning the web" - now browsers implement specific functionality as they choose. The Web Serial API might be in this "HTML5 browser" but not in that "HTML5 browser".

The number is misleading in that sense. It implies a fixed moment in time. And it does that but only in a "before and after" sense.

By @notRobot - 5 months
Does anyone know where I can find old HTML4 templates that used to be all the rage back in the day? (Similar to the few that can be seen here https://www.bryantsmith.com/template/, or used to be provided on hpage.com)
By @sylware - 5 months
I remember from that time those who where trying to do the "semantic web", some kind of complexity abomination... and in the end we got the current scripted gigantic and grotesque DOM abomination locked up/financed by big tech. Yep, I considered that was a loss/loss.

I recall too how the major web browsers did everything to make xhtml dev a massive pain (that was clearly sabotage). In the end, you have to choose doing html "à la xml", or the html "à la sgml" (which is seriously ugly to parse).

The only way to cleanup that big tech lock-down/mess: regulation on critical(utility) web sites with noscript/basic (x)html (like they mostly were a few years ago).

Can we get a clean "better"? Well, if it is as simple (complexity _and_ size) to implement than html parsing, and as stable in time, yeah. As far as I know, it does not exist.

By @Inviz - 5 months
Anybody remembers <command>?