Thank you, PKasting, for being the one to finally say something from the Chrome developers to the "few hundred" people "supportive" of the side tab feature. That it took five weeks to make any response to the issue speaks as much to the disdain with which the developers hold users as did the original fatuous decision to axe the feature without any form of notice, much less a warning.

The feature was well hidden, and it took determined effort to learn about and activate it, even after it no longer required a command line switch. But I'd think it wouldn't even matter how few people were how persistently vocal in their dismay at losing such a useful feature. It strikes me that this is the sort of user interface innovation whose time has so clearly come, whose utility is so patently clear, that it would be seen as a priority to implement it as a selling feature over other browsers.

A strength of Chrome is the ability to run smoothly and quickly with lots of tabs open at once -- a wonderful aid for research. But that ability quickly loses its appeal when one can no longer tell which tab is which because they've shrunken to meaninglessness.

As a software developer myself, a part of my frustration comes from not having an appreciation for how side tabs affected any other plans you have for the browser? Was it somehow actually incompatible with other developments, or was it merely like Google shedding Labs ventures that it no longer considered worth any effort?

Your reply feels as dismissive as the original decision to axe the feature.

[From the +Google Chrome issue tracker]
Status: WontFix
Labels: Restrict-AddIssueComment-Commit

Comment #109 on issue 100319 by BRING SIDETABS BACK

My hope is that ultimately we will add extension-controllable detachable surfaces or similar under the auspices of bug 51084. At that point it will be more feasible to implement a feature like this that has a small but devoted following as an extension.

Until that time, we don't have any plans to re-implement side tabs. There are a number of higher-impact features we're busy working with.

Bugs in our database are not a good place to discuss and debate feature decisions. They're a work tracker for the engineering team to quickly make triage decisions and then either close or schedule the work. I'm sorry no one did that any sooner on this bug and gave all of you folks who were waiting some clarity -- if we weren't going to do this, it would have been good to say so sooner and not give a few hundred people the misimpression that if only they posted enough supportive comments we'd change our minds.

I am closing this bug to further non-committer comments. I suggest that people who wish to discuss this issue use the chromium-discuss mailing list which is a more appropriate forum for that.

I know this is a disappointing and/or frustrating message, and I'm sorry about that, but it's better for us to be clear about our plans than say nothing._
Shared publiclyView activity