On an ultra-wide monitor now and the tabs are small. Sometimes I'll accidentally right-click to 'UNDO' a tab I closed and instead hit 'CLOSE OTHER TABS' which does the exact opposite of what I want. What's worse, any tabs I had open to be viewed later are now gone (and not saved anywhere). There are no options within the addon itself to disable any of the 'close tabs' options. I want to manually control what's closed and what's not without accident mouse clicks removing 30+ tabs at once.
It is a little bit of work, but you can accomplish this yourself via userChrome.css. Check out https://github.com/piroor/treestyletab/wiki/Code-snippets-for-custom-style-rules#hide-context-menu-items-in-the-sidebar-2116 on how to do it.
I'm sure @piroor will let you know his thoughts on your request.
Thank you for your response, irvinm. I'm not going to lie. I think I read that exact page (and another like it from an older Reddit post somewhere) and I have no clue what any of it means. I have absolutely zero knowledge of anything programming (though I can assemble any computer - sigh). I tried understanding what the CSS file is (or how to make one since I seem to be lacking one?) and i have no clue what anything means or .. well you get the idea. A lot of people talk about editing the CSS to make things more customizable but I have a feeling if I did anything, I'd end up deleting some basic functionality of Firefox - even if I backed it up. I'm just THAT awesome! :0(
It's not a "game-breaking" thing and I think we all know how incredible Piroor is for creating this insanely useful addon (and keeping it updated), but just wanted to throw my hat into the ring as it were since I lost a solid 70 tabs last night and was .. oooohhhh ... so unhappy from that misclick. :0(
@LD143, no worries ... CSS isn't the easiest to work with at times. Maybe I can help you. I run with a large number of tabs so I understand your concern. I figured I would disable "Close Tabs to End" and "Close Other Tabs" as well. Here is how you do it.
Finally we need to make sure Firefox will read\process your userChrome.css customization.
This worked for me, so hopefully I wrote it up with all the details so it is understandable and complete.
@irvinm First of all, you rock. Second, thank you! That was EXACTLY what my old non-programming @$$ needed. I must have spent over an hour the other night trying to understand what anyone was trying to say in multiple places but how you laid it out was what I needed - so again thank you for that.
The only question I have after this is that am I going to need to do this every TFT (or FF) update or will this stick for a while unless something breaks it down the line (like the change from old FF to "Quantum")?
Again, thank you. You might have saved me from anxiety medication from tab loss in the future. :0)
You should be good from now on. You won't have to do anything else!
Thank you @irvinm !
@LD143 Sorry but I won't add option to control visibility of common context menu commands on tabs, because they aim to imitate Firefox's built-in commands in the native tab context menu and Firefox itself doesn't provide any option to hide those commands. Indeed Firefox itself also provides "Close Other Tabs" command in its native tab context menu and you still need to use userChrome.css to deactivate it. (Thus, if a future version of Firefox itself implement ability of context menu customization, TST will follow to that.) This is one of design policies on this project.
Understood and thank you for the explanation (and again for the work on the addon!) :0)
@LD143 would you mind closing this issue? Thanks.