Where the Web’s Good Defaults Go Wrong

Browsers ship with a remarkable number of sensible defaults. Semantic HTML, for instance, gives you accessible behavior for free—write a simple <h2> and the browser handles the accessibility wiring without any extra ARIA roles. Responsive design works similarly: the web is responsive out of the box, and it’s usually developers who break it. Even in CSS, display: flex offers a near-perfect default: slap it on a parent and children align horizontally, which is most of what you want.

But not all defaults are so kind. The CSS Working Group keeps an Incomplete List of Mistakes in the Design of CSS, cataloging spec-level issues like:

size should have been a shorthand for width and height instead of an @page property with a different definition

Some of these pitfalls can be corrected after the fact. The box-sizing property is a prominent example—there was a time when adding padding or borders to an element would inexplicably alter its computed width. That confusion is largely behind us now, thanks to a property that should have been the default all along.

The Backspace Hazard

The single worst default, though, was the backspace key. In most browsers, pressing it outside an editable field would navigate you back to the previous page. Countless sessions have ended with a user trying to delete text inside an input field, only to be yanked away to an earlier page with all their form data wiped out. Typing into a form felt precarious, as if one wrong keystroke could bring the whole interaction crashing down.

That fragility may explain why many people gravitate toward native applications. A native app feels like solid ground; a web app, by comparison, can feel like a rickety structure ready to collapse at any moment.

Chrome actually removed the backspace-to-navigate shortcut back in 2016, and Firefox followed suit earlier this year. Yet even years later, the habit persists—many users still hesitate before hitting that key, carefully checking that they are focused on the correct input before proceeding.

Why Defaults and Habits Matter

There are two takeaways here for software design. First, defaults are the most consequential decision you make as a designer—and the hardest to get right. They shape user behavior more than any documented feature. Second, fixing a bad default isn’t enough. Users develop muscle memory around the behavior, and that learned caution lingers long after the problem is solved.