The recent discussion about un-deprecating the HTML <big> element has sparked an interesting conversation about the evolution of HTML elements and their semantic meanings. While the proposal to revive <big> with a new semantic purpose has gained attention, it has also led to a broader examination of HTML's historical development and forgotten features.
The Transformation of HTML Elements
Over the years, many HTML elements have undergone significant transformations in their semantic meanings. For instance:
- The
<b>element evolved from simple bold text to indicating text to which attention is being drawn <i>transformed from italic text to representing idiomatic text such as ship names<small>survived deprecation by being redefined for fine print and legal text
Lost Features from HTML's Past
The community discussion has revealed several interesting features from earlier HTML versions that never made it to modern standards:
-
HTML 3.0 draft included:
- Built-in math mode
<fn>element for footnotes<note>and<person>elements@mdattribute for checksums (predecessor to modern Subresource Integrity)
-
XHTML 2 proposed:
<blockcode>element as an alternative to<pre><code>- General
<h>element for headings <l>element for text lines in poetry or code- Universal
@hrefand@srcattributes
The Case for Big's Return
The proposal to un-deprecate <big> suggests giving it a new semantic purpose: representing the big idea of a document or section. This would be particularly useful for:
- Article ledes
- Important callouts within content
- Skimmable content markers
This proposed semantic meaning would provide parity with <small>, which successfully avoided deprecation by finding a clear semantic purpose in modern web development.
Current State and Future Considerations
While <big> remains technically functional in modern browsers despite its deprecated status, the discussion around its potential revival highlights an important aspect of web standards: the need to balance semantic meaning with practical utility. As web applications continue to evolve, some developers argue that reconsidering deprecated elements with new semantic purposes could provide valuable tools for modern web development.
The ongoing discussion also raises questions about other deprecated features that might deserve reconsideration in the context of modern web development needs, particularly as web applications become increasingly sophisticated and require more nuanced ways to convey meaning and structure.