The New Tab button with vertical tabs should be below the last tab, as in Edge, or fixed at the top of the tab sidebar, or configurable to choose the placement.
Also, double clicking an empty space in the vertical tab sidebar should open a new tab.
The New Tab button with vertical tabs should be below the last tab, as in Edge, or fixed at the top of the tab sidebar, or configurable to choose the placement.
Also, double clicking an empty space in the vertical tab sidebar should open a new tab.
Came here to say exactly that.
Also, when in auto-minimized mode, have the “x” to close the tab somehow remain visible without having to hover and wait for the expanded version.
I came to the community today to make the identical recommendation.
Amazing that such a small thing - as an option in the settings - is “so hard” to implement.
You can do better, just be brave enough.
Cheers.
Yes, I saw the request from 2021, request again every year and they still haven’t implement it yet. No idea why it’s so hard for a very easy change.
PLEASE let us turn off the “new tab” tab. It is now placed on the bottom, and really messes up drag and drop. It has to go! Make a preference to disable or move it.
If it’s too hard to choose the placement (top or bottom), I would like to see it go back the way it was. It just worked before the last update. Dragging tabs and links is a real problem now, daily, and it’s frustrating. Another option, how about hide/remove it? We don’t really need it, there’s CMD-T, which is all I do anyway. Maybe it’s an issue for touch screen users without a keyboard? But on my computer, I never used it, and now it’s just in the way, and has really broken the ability to drag tabs and windows. Another fix might to be just to allow below it as a valid drop target for the drag and drop. That would probably completely fix the issue.
It would be appropriate, expected to support right-clicking in the area for actions, including new tab.
If you have it available, center-click or mousewheel-click, still kills tabs.
If you’re a vimium user, you can add (non-default) keybinds for “close tabs right”, “close tabs left”, and “close other tabs”
It’s a big lift to compile Chromium at all, plus they maintain a hefty patchset.
I think Vertical Tabs is an upstream feature of Chromium – oh, jk, 2011
“Sidetabs were an experiment that didn’t pan out. They’re in a half-working state and
should be removed, says Glen. We’ll try to come up with other approaches for this use case.”
https://issues.chromium.org/issues/40640335
Related, additional
Removed sidetabs — patchset: https://issues.chromium.org/issues/40640156
More pining for the fjords: https://issues.chromium.org/issues/40098488
The timeouts and precision required for tab drag out of and especially into another window is quite frustrating, 500ms+ of latency, blinding hope the drag placement is good enough to transfer the tab.
Just wanna add my voice to the “revert this change or make it a setting” crowd. I much preferred the old UX. To add to that, I think the change actually brought up two separate issues:
Just no! You are on of the people how just has destroyed Braves “new tabs” Its annoying as all hell to have it be after the last tab!
It would be great if the New Tab button in vertical tabs could be placed below the last tab (like in Edge) or fixed at the top, with an option for users to configure its placement. Additionally, allowing double-clicking on an empty space in the sidebar to open a new tab would improve usability and streamline the tab management experience.
I’m not keen on the new New Tab placement either.
I can see how it might be an improvement for mouse enthusiasts, but it definitely interferes with drag-and-drop operations, and from a visual standpoint it takes my brain a second to register that “New Tab” is not a normal tab. For example, it makes it harder to find the last thing I opened whenever I glance at the sidebar.
Also, I noticed that there is a horizontal rule in Private Mode that is not present in the standard browser:
Anyway, a config setting for the New Tab button would be much appreciated!
I’m not liking the New Tab location on vertical tabs with the latest update (v1.75.175). I’d like to suggest with others that this should be a radio button setting:
I’m one of the users that uses the New Tab shortcut instead of the button personally.
The new tab location is unbelievable. If you use the browser normally, clicking the bottom item to switch to your last tab becomes muscle memory.
I spent about five minutes repeatedly clicking the last tab, trying to return to my previous one lol my brain just wasn’t registering that it now said “New Tab.”
I’ve been using Brave since shortly after its launch, and they usually don’t make changes like this. They’re typically thoughtful and provide options to customise features like this.
Unless an option to change it is added, I’ll have to switch to another browser.
As this post is from Jun 2023 do we need to create a new thread?
First of all, a huge thanks to this community and to the developers of Brave. I am a huge fan.
I’ve been using Brave for a while now and it’s excellent overall. I love the direction it takes from Chrome/Chromium and I love how optional most things are; that’s why I’m shocked there’s no optionality for the placement of the New Tab button in Vertical mode.
I strongly prefer it at the bottom of the screen where it was previously to the point where I’ll be going back to the old version until said option exists.
Another thing is that the New Tab button has the text New Tab which ends up creating a new tab with also the text New Tab right above it therefore they both look like new tabs title New Tab.
Come on people. :P’
Uhh I think you’re going to struggle there lol… all other browsers seem to have new tab button immediately after the last tab, and Brave was the exception.
I much prefer the new placement, although it could be implemented better:
I registered here only to have a place to vent my pent-up rage over the new position of the “new tab” button, which I constantly try to close
Has there been any news on this front? Wondering if we need to open an issue on GitHub to get a set of developer eyeballs on this.