Eleven Years for Vertical Tabs: Why Good Features Stall in a Market Leader's Backlog

This July, a Chrome update finally brought vertical tabs to my browser. Google had started rolling them out that April.

Vivaldi had them in 2015. Edge followed in 2021. Arc made the sidebar its core design in 2022. Eleven years later, the browser with the biggest market share finally came around.

Safari on the Mac still has no vertical tab layout. Apple's own documentation lists two layouts, "Separate" and "Compact," and both are horizontal.

The usual explanations go something like this: the audience is too small, the change is too expensive, and extensions can fill the gap.

None of them holds up well here.

Vertical tabs are an option. Nobody is taking horizontal tabs away. If you don't want them, you never turn them on, so nobody's muscle memory gets hurt.

Chrome extensions can't change the tab strip, which is the browser's own territory. So "there's already a workaround" doesn't work either.

And once you have twenty-plus horizontal tabs open (hardly unusual these days), each one shrinks to a tiny icon and you can't tell them apart. Nothing fixes that. At that point the feature simply stops working.

An optional feature with no workaround and an obvious pain point still waited eleven years.

I can't see inside Google, so this is a bold guess: the real answer is much simpler, and much harder to say out loud. Someone with decision rights just didn't like it.

In a big company's backlog, nobody writes "I don't like it." It gets translated into priorities, resource allocation, and risk assessment, then filed in a document that sounds perfectly reasonable. In my experience, the people in the room usually know that isn't the real reason, and nobody needs to say so.

That's how a market leader's blind spots grow, one layer at a time. It's rarely one big mistake. It's a long run of "not now" and "there's something more urgent."

There's a line that gets passed around a lot online. Supposedly Nokia's CEO said it at the press conference announcing the Microsoft acquisition: "We didn't do anything wrong, but somehow, we lost."

I couldn't find an original source for that quote. It may well have been made up.

But it spread for a reason. It hits a nerve: a company can write a sensible document for every decision, run each one through the proper process, and still lose. And there's no next chapter.

Because "we didn't do anything wrong" hides a lot of things that never got written down.

So I'm not that surprised that Google's AI lineup today, Gemini, NotebookLM and the rest, feels bolted together from separate parts. (To be clear, I'm not bashing Google. I still love NotebookLM.)

Have you run into this in your own product? Which feature got blocked, by whom, what reason went on paper, and what happened next?

And in your career, was there a path you didn't take because someone didn't like it?