Unsolved Why is it so easy to accidentally close tabs??
-
@ryofurue Adding an edit I was not allowed to make to the last post:
I'm looking again and the X is activated IF the tab is active, which is bizarre, because if that's not the case, how am I accidentally closing tabs so often? Good question, and I don't have the answer right now.
-
@OakdaleFTL What if I don't want accordion display style (which I don't--it takes up too much real estate)? Why can't we just expect the close function to work properly?
-
@luetage Or we could expect the close tab function to work properly and not expect users to have to change their behavior instead.
-
@SaphiraBlue Well, good luck with that. You are talking to community members here, we can’t change a thing. You have been presented with various alternatives to make tab closing/handling easier for you. If you can’t accept any of it, your only way forward is to either write a bug report or a feature request.
-
@luetage I don't think it's necessary to be condescending just because I don't believe users should have to adapt to poor design.
I was also not aware that this was not a way to contact anyone from Vivaldi proper, or I wouldn't have bothered to post here. Their support page implies that this is a place to contact them and doesn't offer any obvious alternative.
So sorry to have troubled you. Have a nice day.
-
@SaphiraBlue I wasn’t condescending, you are overtly sensitive. This is a place to receive community support and it wasn’t a mistake posting here, you got all the information you need and you know how to progress from here. If the solution you imagine simply isn’t there, we can’t force it into existence, this you have to accept.
-
@luetage "Well, good luck with that" is pretty condescending. Bye now.
-
Consider modifying Settings > Tabs > Active Tab Minimum Width to 180 pixels or other acceptable value to avoid accidental closure of active tab. For example, instead of active tab appearing as highlighted below:
it will appears as:
-
Thanks, but it's not active tabs that close when I click on them. It happens when I switch to inactive tabs--there's no need to click on the active tab--so that's not going to solve the problem unless there's something I'm missing here?
-
Ignore following advice as on retrying it does not resolve issue; sorry.
Understood. Instead, under Settings > Tabs > Tab Options try the options as highlighted below:
-
@SaphiraBlue said in Why is it so easy to accidentally close tabs??:
[. . . You pasted a nice screenshot here . . .]
And the X is immediately activated when you hover over the tab, which is how I got this shot. So Vivaldi is programmed to assume you want to close the tab rather than switch to it, which is counterintuitive.
I agree. That is exactly the same as my complaint I mentioned earlier! I have exactly the same problem.
My feature request would be:
"If the tab is narrow, the X button should be shown only after the tab is activated (clicked upon)."
If there is no request like this, I'll submit it to the feature request forum. (But, I'll search the forum.)
-
@SaphiraBlue said in Why is it so easy to accidentally close tabs??:
@OakdaleFTL What if I don't want accordion display style (which I don't--it takes up too much real estate)? Why can't we just expect the close function to work properly?
First, the Accordion style tabs only takes up at most the width of the window: That's the point!
But -even if you thought the Tab Bar took up too much space — why keep it on-screen when you can easily hide/show it as you please?
(I generally run three profiles all the time. But in the main one I usually have between 120 and 200 tabs open (with a few Workspaces and Windows open). Imagine trying to keep track of them — without using all the features of Vivaldi!)
I don't understand what behavior you want...
Consider this screenshot:
That's a window pinned to the right side of the screen. The number os tabs it contains doesn't matter to the display. You can scroll left or right through them.
BTW: Are you using a track pad?
-
@SaphiraBlue disabling the close button seems to be the only feasible option right now.
You will of course have to use other means (as already described) to close tabs then.The option to only have a close button on the active tab (like
Firefox) is still missing. -
@becm Am I wrong in remembering an Accordion Tabs option for FireFox?!
I seem to recall it being quite popular... -
@OakdaleFTL said in Why is it so easy to accidentally close tabs??:
I don't understand what behavior you want...
I want the close function on tabs to work properly. That’s literally all I want. I’m astonished that that seems to be so surprising.
That's a window pinned to the right side of the screen. The number os tabs it contains doesn't matter to the display. You can scroll left or right through them.
Okay? But the way you like to use your tabs isn’t necessarily the way anyone else likes to use theirs.
BTW: Are you using a track pad?
Yes. Why does that matter?
-
@becm said in Why is it so easy to accidentally close tabs??:
The option to only have a close button on the active tab (like
Firefox) is still missing.Sounds like this is the problem, then, and what needs to be fixed/added.
-
I bumped into accidentally closing tabs yesterday and wondered what the heck happened.
I then went looking for a reopen recently closed tabs but could not locate it. Made a search and came across Tools -> History which has helped somewhat.It would be nice if recently closed tabs where remembered and could easily be reopened again.
Tutorial creator. Freelance web designer/developer creating web sites with WordPress. I give feedback in relation to design, UI, testing and more to various companies on products they create. https://easywebdesigntutorials.com/about/freelance/
-
https://help.vivaldi.com/desktop/tabs/opening-and-closing-tabs/#Reopening_recently_closed_Tabs
https://help.vivaldi.com/desktop/tabs/window-panel/#Recently_Closed_Tabs
Also:
I have Show Closed Tabs mapped to Alt+Z but those are the defaults.
-
To summarize the problem:
The default Vivaldi behavior is . . . when you keep opening tabs, the width of the tabs eventually becomes so small that the tab-closing button occupies most of the tab area. Then, when trying to activate a tab, you accidentally close it and are annoyed.
In the feature request forum, there have been two requests that, if implemented, would solve the problem in one way or another.
-
Add the ability to set the minimum tab width (whether the tab is active or inactive). This request, from 2018, has gained some support but haven't been implemented.
-
Show the tab-closing button only when the tab is active. This request didn't get many upvotes and have already been archived.
I mean to propose a variation on request 2 above.
- Hide the tab-closing button when the tab is inactive and too narrow.
But, looking at the fate of request 2, I'm discouraged. Also, I think that request 1 is a better solution.
[Aside] The original problem I described at the top, is a real problem. Instead of, or in addition to, offering some options to fix it, Vivaldi wants to change its default behavior.
Not only about this issue, but in general, I imagine there are a lot of newcomers who try Vivaldi out, is annoyed by some of its default behaviors, and quietly ditch it.
Only the minority of those users who are frustrated will post here in the user forum. So, if the default behavior is suboptimal, offering an option or workaround isn't good enough.
-
-
As a brand new user, I found this behavior to be confusing and problematic as well. Restoring tabs is mostly useful good enough, but not always. A good side effect was that it encouraged me to learn how many options I have available.
I do agree, however, that an option to Hide the Close Tab button on background tabs would make a lot of sense. Combining it with sensitivity to tab width would be fantastic.
Single Close Tab button on the right of the tab bar is related and would be a better workaround for some (but not all people).
For now, I'm trying out the option of totally removing the close button on the tab, while also enabling double-click to close.
I'd vote for a #3 proposal if it came around.
