Skip to content
Tech News
← Back to articles

Antiquated HTML Snippets and Artefacts

2026-09-08 | original
read original get Jon Duckett "HTML and CSS: Design and Build Websites → more articles
Why This Matters

A look back at the HTML snippets developers once had to add not because the spec required them, but to work around browser wars, vendor plugins and third-party integrations tags like X-UA-Compatible or Google's Chrome Frame flag. It's a reminder that much of the web's markup is archaeological residue of platform politics, and that copy-pasted boilerplate can outlive its purpose by a decade or more.

Key Takeaways
Worth a Look

Jon Duckett "HTML and CSS: Design and Build Websites — If reading about relics like the X-UA-Compatible meta tag made you curious about what modern markup actually looks like, Duckett's classic is a beautifully illustrated way to ground yourself in current HTML and CSS. It's the kind of reference that makes the difference between cargo-culted snippets and markup you actually understand.

See Jon Duckett "HTML and CSS: Design and Build Websites on Amazon → Affiliate link — we may earn a commission on purchases, at no extra cost to you. Product picked by AI based on this article; it is not a tested recommendation.

With ever-changing devices, browsers, operating systems, form factors, specifications, personal preferences, tooling, and corporate interests, the web is in a constant state of flux. As a result, so is the HTML we write. For every line of the HTML specification itself that has changed since the language’s inception, there are many more bits of HTML that have seen what I’ll call ‘environmental’ changes. Adaptations to differing browsers, extensions, integrations, and systems which we find HTML existing in.

This article doesn’t cover once-specced but now obsolete bits of HTML but instead looks at all the snippets that have wormed their way into websites as result of, or in combat against, third-party integrations, browser competition, vendor extensions, and platform-specific hacks. The bits of HTML that were included for reasons, and which have been forgotten for present irrelevance. The snippets that live on only in the markup of sites from bygone eras and in the minds of those who fought during the browser wars.

X-UA-Compatible

< meta http-equiv = "X-UA-Compatible" content = "IE=edge" >

In an age where browsers changed quickly and version-specific behaviours weren’t unheard of, it was deemed necessary to signal compatibility with specific versions of browsers with the X-UA-Compatible meta tag. Here the content attribute reads IE=edge , meaning that the target is the highest supported document mode in Internet Explorer (IE).

As outlined in the documentation, there are other values than edge . One can also supply a value of 5 through 11 to correspond with the associated Internet Explorer version, or EmulateIE7 through EmulateIE11 to enter into that version’s mode, but only if a valid DOCTYPE is declared, otherwise falling back to quirks mode.

< meta http-equiv = "X-UA-Compatible" content = "chrome=1" >

Before Chrome took over the market, Google released an Internet Explorer plugin called Google Chrome Frame. Installable in Internet Explorer versions 6 through 9, it rendered websites in Chrome’s modified WebKit engine rather than Internet Explorer’s Trident engine if they had the tag set.

< meta http-equiv = "X-UA-Compatible" content = "requiresActiveX=true" >

requiresActiveX was used to prompt Internet Explorer 10 to switch to desktop mode if in Metro mode, which didn’t support plugins.

... continue reading

Explore topics: html x-ua-compatible internet explorer meta tags browser wars
Related:
Limit bets on clinical-trial outcomes being placed on prediction markets
Apparently CodePen 2.0 sends data to their servers as you type
Programming is Art
Catching Crumbs from the Table (2000)
Briefing Chat: How 1,000 pairs of buried underpants helped measure soil health

© 2026 GoKawiil

About | Editorial Policy | Contact