Why '98% browser support' still leaves 150 million people staring at a broken page

A high percentage only reads as impressive when the stakes are trivial. Winning the lottery or acing exams 98% of the time is remarkable, but a restaurant that poisons diners 2% of the time, or an employer who pays wages 98% of the time, is failing at a basic obligation. Context, not the number itself, determines whether 98% is a triumph or a scandal.

Applied to the web, the same math turns damning. Shipping a feature that works for 98% of browsers means abandoning roughly 150 million people, the equivalent of a venue turning away two out of every hundred returning customers in the name of an ‘improved experience.’ Worse, global support stats rarely match a specific site’s audience: the author found that nested CSS, declared safe and ‘widely supported’ since 2023, actually covered only about 70% of one client’s real visitors over the prior year, leaving 30% behind.

The takeaway is a case for progressive enhancement over convenient averages. Robust engineering is measured by how gracefully it handles the edge cases, not by how well it serves the majority. If a shiny new feature can’t degrade gracefully, calling it ‘widely supported’ is a lazy shortcut that quietly writes off the people it breaks for.