All these cool new features make me sad that there still isn’t a tab groups or tab mix plus for the new versions, because in the end they have bigger usability benefits :(
Ooh, I just got something called Simple Tab Groups installed. Last I checked, I’m sure it didn’t work yet. It appears to load all tabs, which is probably on the heavy side, but at least I got an initial good feeling here :)
Multiple rows of tabs is still missing from the original experience, as was brought by Tab Mix Plus.
Don’t know about that particular add-on, but there’s a discard() API it could use to unload the tab from memory. This is regardless of whether it’s shown or hidden.
I’m sure that’s great and all, but I’m not in a position to cook this stuff up or even really contribute to development, I just want to keep my efficient workflow :(
On the subject of multi-row tabs, I could try the CSS hack(s) on for size if I have time soon. And also see if I can alter the behavior of closing tabs like with TMP, but I wish there was something more official.
Maybe this is a case of feeling entitled to things faster than they can happen and I’m pretty much ok with it. Usually people are impatient when they shouldn’t be. The situation just isn’t optimal as far as the trade-offs are concerned :/
There’s an API for hiding individual tabs, but hiding the “official” tab strip and showing a custom add-on implementation is not yet done. The addons team has written a lot of new code for these new APIs to exist. Some of those APIs serve much less addons than others, so they’ll have to wait. This is unless add-on developers themselves step up, which has been the case for the more popular ones.
Regarding CSS hacks, you can try those but heres my 2 cents:
executing someone else’s CSS in Firefox’s internal UI code looks harmless but it’s the equivalent of running an untrusted executable file from the internet
we still work and iterate in the existing tabstrip. They will always need to be updated and maintained well so they don’t break your browser
Maybe Simple Tab Groups loads all tabs and warns about leaving pages with forms when changing groups because of the API for hiding, dunno.
I did actually create a userChrome at https://github.com/mjtorn/firefox-tabrow-userchrome though it is based off the Internet. It’s ok for my laptop but rearranging tabs would have to be ok for serious work :(
What’s the big attack vector here?
Either way, seeing the tabs in rows and having some progress with Simple Tab Groups makes me feel good and eager to see more :)
It’s a bit obscure, but our internal, chrome-level CSS can use non-standard features to execute JavaScript at the highest privilege level and that allows subprocesses, reading files from disks etc.
Relatedly, Scott Helme wrote about the feature in https://scotthelme.co.uk/csrf-is-dead/
All these cool new features make me sad that there still isn’t a tab groups or tab mix plus for the new versions, because in the end they have bigger usability benefits :(
But there are tab management addons like tab groups, built on Firefox containers.
Ooh, I just got something called Simple Tab Groups installed. Last I checked, I’m sure it didn’t work yet. It appears to load all tabs, which is probably on the heavy side, but at least I got an initial good feeling here :)
Multiple rows of tabs is still missing from the original experience, as was brought by Tab Mix Plus.
Don’t know about that particular add-on, but there’s a
discard()API it could use to unload the tab from memory. This is regardless of whether it’s shown or hidden.I’m sure that’s great and all, but I’m not in a position to cook this stuff up or even really contribute to development, I just want to keep my efficient workflow :(
On the subject of multi-row tabs, I could try the CSS hack(s) on for size if I have time soon. And also see if I can alter the behavior of closing tabs like with TMP, but I wish there was something more official.
Maybe this is a case of feeling entitled to things faster than they can happen and I’m pretty much ok with it. Usually people are impatient when they shouldn’t be. The situation just isn’t optimal as far as the trade-offs are concerned :/
There’s an API for hiding individual tabs, but hiding the “official” tab strip and showing a custom add-on implementation is not yet done. The addons team has written a lot of new code for these new APIs to exist. Some of those APIs serve much less addons than others, so they’ll have to wait. This is unless add-on developers themselves step up, which has been the case for the more popular ones.
Regarding CSS hacks, you can try those but heres my 2 cents:
Maybe Simple Tab Groups loads all tabs and warns about leaving pages with forms when changing groups because of the API for hiding, dunno.
I did actually create a userChrome at https://github.com/mjtorn/firefox-tabrow-userchrome though it is based off the Internet. It’s ok for my laptop but rearranging tabs would have to be ok for serious work :(
What’s the big attack vector here?
Either way, seeing the tabs in rows and having some progress with Simple Tab Groups makes me feel good and eager to see more :)
It’s a bit obscure, but our internal, chrome-level CSS can use non-standard features to execute JavaScript at the highest privilege level and that allows subprocesses, reading files from disks etc.