Pinned tabs in Multiple Containers
I routinely leave my most used socials in pinned tabs, meaning I have 2 plurk tabs & 2 reddit tabs open all the time. When the browser restarts, 1 of the 2 tabs will reload in a new tab and ask if I'm sure I want to open in the container that the pinned tab that loads properly loaded in. (I hope you can parse that, that's the simplest way I could find to word it.) Since firefox won't let you ctrl+W on a pinned tab, I then have to unpin and close the tab that didn't load right, & pin the new tab.
I use the latest version of firefox in linux mint 21.1. I'm on the latest kernal, but this has always happened (since I switched from chrome back in June).
(I also wish you could simply close a pinned tab, I used that a lot on chrome too.)
منتخب شدہ حل
Your pinned tabs are not using containers in your screenshot but you have assigned them to containers so they will try and open in new container tabs. Unpin them, open them in containers and then pin the containerized tabs.
اس جواب کو سیاق و سباق میں پڑھیں 👍 1تمام جوابات (3)
You can close a pinned tab with a middle-click on that tab or via the right-click context menu as you can't do this easily with the keyboard (this would require keyboard navigation). Does it make a difference if you load pinned tabs on_demand via the about:config page?
- browser.sessionstore.restore_pinned_tabs_on_demand
منتخب شدہ حل
Your pinned tabs are not using containers in your screenshot but you have assigned them to containers so they will try and open in new container tabs. Unpin them, open them in containers and then pin the containerized tabs.
cor-el said
You can close a pinned tab with a middle-click on that tab or via the right-click context menu as you can't do this easily with the keyboard (this would require keyboard navigation). Does it make a difference if you load pinned tabs on_demand via the about:config page?
- browser.sessionstore.restore_pinned_tabs_on_demand
Is that solution meant to be for the container problem, or closing tabs with ctrl+W? If it's the latter, that didn't work. The former was solved by @zeroknight.