Pinned tab cannot be closed
cultoo last edited by gaelle
Pnned tab cannot be closed OS X 10.11.4
See following screenshot: https://forum.vivaldi.net/uploads/attachments/80893/ScreenShot2016-05-17at09.49.19.png
Did you make pinned tabs closable in Menu/Tools/Settings/Tabs?
Pinned tab cannot be closed
…& in other breaking news, water is wet, fire is hot, anthropomorphic climate change is real... :)
I like learning about the preferred workflows & habits of other users, in case i can learn & adopt any handy ideas for myself. In this case, could you kindly pls explain why you want pinned tabs to be closable without first unpinning them? In my mind that ruins a major benefit of having pinned tabs. I'd welcome other opinions, pls.
The_Solutor last edited by
Even if the closeability of a pinned tab was implemented, because someone did request that "feature", I still think is an oxymoron
Menu/Tools /Settings/Tabs/Tab Features/Pinned Tabs/Close as other tabs
@Ayespy Why on earth wouldn't "Close" a pinned tab be the default condition? I can't think of why anyone would not want that option on a tab menu with many others..
@shoq -- Why on earth would "Close" a pinned tab be the default condition? I can't think of why anyone would want that option on a tab menu..
...& yet apparently you do. Therefore, can't you invert your thinking & imagine the counter-possibility that other users might have alternative desires than yours, no matter how certain of your own opinion you might be?
Choice; V aims to be all about choice.
@shoq - members of this development team invented pinned tabs years ago in OldeOpera. The default there, as pinning might imply, was that the tab could not be deleted - only un-pinned and then deleted. The reason was that pinning a tab meant you wanted to keep it. If you want to keep it, you don't want to accidentally delete/close it. So it stays. If you change your mind and want to get rid of it, you un-pin it, and then delete it. That was the idea behind the original concept of pinned tabs.
Thanks. Since posting this,I discovered there's a preference for adding close to the pinned tab :)
I guess if it was already there, people must certainly want it. As for whether it should be "default." well, is on every other browser, so why not here?
Be that as it may, it's rarely a good idea to presume to know how users work or regard a common feature. I use pinning to keep things current for the day, often as part of the project I am working on. I might have 5, 10, even 15 pins on some days. Why should I do 10+ clicks to close them when 5 would do? (I wouldn't mind a Close All Pins option, too).
Others who posted here probably do something similar.
@shoq: Not the only idea Firefox and Chrome stole from Opera and then turned on its head, leading millions of users to become used to the idea that a feature "should" be the opposite of the way (and the reason) it was invented. The fact that something has been corrupted and then become the default by virtue of ignorance of the original concept, is not a signal, in my view, that the Vivaldi developers should ignore the original concept. It only says to me that it's a worthwhile idea for the developers to provide an option (as they did from the very beginning in this instance) to do it the new, "wrong" way.
You do pinned tabs your way. I do them the original way, ie use them as a tab that I wish to be present always and forever on the bar, for me to access any time I think of it (which may be several times in a session on any given day), but off to the side when I don't need it in the work flow. They are like bookmarks that you don't have to wait to open, because they are already on the tab bar and in memory.
(Interesting side note) I never used pinned tabs in Chrome or NeuOpera because it was pointless to pin them if you could accidentally close them. I also avoided, for instance, the "open in new tab" context menu item because it always made me crazy that the new tab would open in the background and then I'd have to go hunt for it. Instead, I resorted to copying a link address, opening a new tab, and then past-and-go. I couldn't even remember that shift+middleclick on a link would bring it up front while opening. Who would even think of trying such a thing? So it works both ways. Why did firefox and Chrome steal a concept and then break its behavior which already worked "right" in the first place?
@Ayespy And here I thought the whole philosophy of this browser was to let users opt-in to features, rather than according to Chrome's very austere philosophy. Yet here's one I want to use, and you're already telling me I'm not doing according to "original intent." (To me, a browser is a tool, not a constitution : )
I'd think MOST users won't be coming from Opera., as in the U.S., it's never had much marketshare. They will be coming from Chrome , Firefox, where, regardless of history, it's a feature they are used to on their Tab Context menu. This is why I suggested it be default. It is for most U.S. users already, and it's not the sort of thing new users will rush off to find a preference for—just as I didn't. That's why I came here to suggest it. (Very few users will surf a preference system until they've been with a tool for awhile. More often they stumble across it, as I did, while looking for something else).
As for how you use Tabs, vs. how I do, I've been using browsers since Mosaic 0.8. I'd never known there was a "right" or "wrong" way to use any specific feature. I use pinned tabs your way about 1/2 the time, and the other half, merely to COMPRESS items on my tab bar when I need things open, and accessible, but not necessarily visible and eating up valuable tab bar real estate.* I know at least 5 people off the top of my head who use them exactly the same way, so again, not sure of how much of an outlier I am here. But hey, maybe we need a Pin poll to find out? :)
Thanks for the replies!
- Is there a plan for a multirow tabbar? It's still one of my best reasons for liking Firefox. The "multirow plugin" handles them quite well. A Chrome extension never got it right.
@shoq: That's why "right" and "wrong" are in quotes. It's an ironic way to point out that right and wrong as to browser feature preference are purely points of view, and without any basis in natural law. The aim of my comment was to point out that there is a REASON why certain Vivaldi features are the way they are, it's not arbitrary or random, but rather based in the history of the developers, just as your preferences and mine are rooted in our histories. It is as valid a view (if not more so) than "You should observe this convention because everyone does it that way." That stance leads to stasis, not progress.
I've commented more than once that I've witnessed hundreds of new users coming to Vivaldi because they want something different, and then watched them complain that it's not the same as their old preferred browser. They want things changed they way THEY want them changed, while otherwise keeping things they like and are used to. I suppose when entering a new environment, one will fare well if they are prepared for it to be . . . . . a new (different) environment.
The kewl thing is that Vivaldi aims to essentially have an option for nearly every imaginable preference in time, and that they are moving more rapidly in this direction than any development process I have ever seen.
And while I never used Mosaic (we used personal computers starting in 1977 but obtained our first web-capable machine with an internal modem in about '94 - and went straight into Netscape Navigator), I've sought out different and more efficient ways to do things with software from the very beginning - and it's what brought me to first, Opera (ver 5), and now Vivaldi. I have never, in my life, used IE, Firefox or Chrome as a primary browser. Never could get comfortable with any of them. I've experimented with lots of browsers, but my defaults have remained consistent - Straight from Netscape to Opera to Vivaldi. For my purposes, each of these were the most efficient when I discovered them.
Steffie last edited by Steffie
Yes, but this is a good browser, unlike C & FF. V users are discerning, well-bred, talented, & fastidious, unlike C & FF users [note: yes, those words have a fairly high probability of being tongue-in-cheek].
In seriousness though, as people have already indicated, there is a robust argument can be made that the act of pinning a tab implies a desire for that tab to be permanent, or semi-permanent, for which scenarios closing is a rarity or non-event. In that mindset, your suggestion is, respectfully, sub-optimal.
@shoq -- I think it might behove you to go back & read Jon's original manifesto for why he chose to co-found Vivaldi, & the user-cohort targeted at least in the early period. The world does not need any more crap browsers, but since the demise of O12.x has sorely lacked a web-enthusiast power-user browser. V is already doing a fine job of meeting that need, & will only get better & better.
Some users will always prefer other browsers though, for rationales that are valid to themselves. You might well be one of them. Or not. However IMO V would be entirely shooting itself in the foot if it were to lose its way, reverse direction, & become "just another Chrome clone". People like me detest & revile Chrome, so the advent of V was/is a truly wonderful thing. Examples like V's pinned tabs philosophy speak directly to my sensibility; Chrome's way is stupid [for me].