21–30 of 243 posts
They mention tab groups. Mozilla, why do you play with my feelings?
The containers addon does grouping, sorting, color coding, auto group association, and sandboxed cookies. Is there something else you're looking for?
Earlier quoted context omitted.
They are referring to hiding individual tabs, not hiding the horizontal tab bar. The legacy extension they are referring to is Tab Groups [0]. It allowed you to separate the tabs of a single session into groups. Selecting the active group would hide the other tabs. [0] https://addons.mozilla.org/en-US/firefox/addon/tab-groups-pa...
Oh! Ok. I've actually used this extension a bunch, but it was several years ago. Wasn't it part of Firefox at one point? Or, am I misremembering.
Earlier quoted context omitted.
I thought the gaining philosophy here was to make "destructive" operations easy to undo, rather than having warnings and confirmations before carrying them out? Quitting Firefox and then starting again and restoring all tabs fits well with easy to undo.
I don't see how it can undo everything, if you'll lose data in the process. Not every open page is static and some can have user input and what not. Exiting the browser will wipe it all out, and restarting it isn't going to help. So confirmation for Ctrl+Q is a must, there is no question about it. And if you don't want it - they can make an option that can turn it off.
Not only that, but it can take a significant amount of time to restart the browser and reload the tabs you had open.
So just in terms of time wasted, accidentally quitting the browser and having to restart it is awful and painful compared to just canceling the quit.
They mention tab groups. Mozilla, why do you play with my feelings?
What are you referring to? The containers addon does grouping, sorting, color coding, auto group association, and sandboxed cookies. Is there something else you're looking for?
Earlier quoted context omitted.
Something that drives me nuts is how stateful about:config options are. If you set them once, either through about:config or using a user.js, they will stay like that forever unless you explicitly unset them.
Wow, totally disagree. Instant-persistent-on is a much better and more intuitive experience than old "Cancel, Apply, Ok" settings paradigms.
There exist good cases for instant persistence, like switching themes when you want to see the effect immediately before you decide.
Other than that it's really nice to be able to cancel everything when you realize you've messed up.
It's crazy to me that Firefox's original selling point was tab management, and today Chrome's is so much better.
Earlier quoted context omitted.
Something that drives me nuts is how stateful about:config options are. If you set them once, either through about:config or using a user.js, they will stay like that forever unless you explicitly unset them.
Wow, totally disagree. Instant-persistent-on is a much better and more intuitive experience than old "Cancel, Apply, Ok" settings paradigms.
Say I write a user.js file with a few options. I can't have the typical dotfile model, where removing options from this file will lead to defaults on the next run. I need to unset them. Explicitly.
Thus, using a dot file to set up Firefox (user.js) is incredibly clunky and people don't use this much.
Mozilla should fix no exit confirmation for Ctrl+Q. It's just too easy to close the browser this way, and extensions that offered this feature aren't working anymore. It's really a problem in general, there is no way to make an extension that customizes browser behavior itself (rather than page behavior), since WebExtensions can't do that.
They mention tab groups. Mozilla, why do you play with my feelings?
What are you referring to? The containers addon does grouping, sorting, color coding, auto group association, and sandboxed cookies. Is there something else you're looking for?