-
Notifications
You must be signed in to change notification settings - Fork 67
Implement reverse tab order #5
Comments
My strong suggestion is to not do this. It was an interesting experiment, but led to literally no end of problems, and totally wasn't worth it. 😉 |
Perhaps there could be a better way to implement this feature that wouldn't lead to so many bugs as last time. |
It wasn't just bugs, as much as that everyone who wanted it wanted it to act slightly differently, so no-one was happy with the one checkbox. (For instance, should ctrl-tab take you up or down? When opening a new tab, should it go at the top or the bottom? Should pinned tabs stick to the top or the bottom? Those are just a few examples off the top of my head where different people wanted different things, and it leads to a combinatorial explosion of possibilities for little real usability gains.) |
Rather than reverse the tab order, an option to open new tabs at the top would be immensely helpful. When I have a long list of tabs, I'd rather get thrown to the top of my list because that's where all my pinned tabs are. I also like this because it stacks my tab history more chronologically with my newest visited tabs at the top. |
That sounds like a different WebExtension, and I think @autonome might have already wrote it… :) |
Interesting. Do you have a link? |
https://github.com/autonome/Always-Right maybe? (He was talking about it in IRC yesterday or the day before, but didn't mention which one.) |
That's exactly what I wanted! Thank you. And thanks @autonome ❤️ |
Life begins today, @kumar303.
…On Wed, Aug 16, 2017, 01:55 Kumar McMillan ***@***.***> wrote:
That's exactly what I wanted! Thank you. And thanks @autonome
<https://github.com/autonome> ❤️
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADDt4jAeqjvOpJJ7pxMF898BUsR-_6Fks5sYdtzgaJpZM4NwsRK>
.
|
This will probably never happen, closing this bug! |
No description provided.
The text was updated successfully, but these errors were encountered: