Years of Browser Work, No Prefix in Sight
Getting a CSS feature standardized and unprefixed across all browsers is rarely a quick task—but for the appearance property, it turned into a multi-year slog. A thread from Bocoup highlights just how stubborn this problem proved to be.
The story starts with Firefox asking Bocoup to fix issues in how the appearance property handles form elements. The challenge quickly became clear: each browser had rolled its own implementation, leading to inconsistent behavior across engines. The project began roughly two years ago and didn't wrap up neatly.
A Slow Grind Toward Consistency
Bocoup's work went well beyond writing a patch. The team performed extensive research, authored a suite of tests, and helped overhaul both the HTML and CSS specifications. Adjusting the spec alone wasn't enough, however. They had to demonstrate that browsers could drop the vendor prefix without breaking live sites—an earlier attempt had done significant damage and had to be rolled back.
Eventually, the effort paid off. The change landed in Chrome, Firefox has a tracking bug for it, and Safari has an open bug as well. There's also community interest in coordinating a release across browsers.
If you want a sense of how rare and fragile success is in cross-browser work, the timeline here is the lesson. Shifting a property from a prefixed, quirky state to a shared standard isn't a sprint—it's a process that requires testing, specification updates, and substantial patience. Bocoup details some of their thinking on ShopTalk 407 along with Brian Kardell.
