-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Add inactive tabs tray group #20349
Comments
Created #20507 for the telemetry. |
Could the inactive tabs feature be deactivated in the settings? |
Hi again. I have a question: are inactive tabs being synced with other Firefox instances as well? I have no other device to check at the moment. Thank you. |
Something in the implementation here reset the setting to 30 days and is killing tabs for a bunch of folks: #20629 |
Almost certainly this line... The defaults were changed to always close tabs older than one month and unset the manually close option, based on the inactive tabs feature being enabled or not. As I explained in #20650 (comment), this completely breaks Firefox's reliability for a multitude of users. I doubt almost anyone has a way to recover their old tabs. |
It's not only a default value problem: I changed its value from the options and reverted it to "close manually" and the tabs have been wiped away anyway. |
I don't understand the motivation for this feature at all. There are several problems as it currently stands:
It doesn't seem like a very well thought through change. Was any UX research done on this? |
I filed #20684 for adding an option to disable this feature. |
Hi folks, let me preface this by saying thanks for the feedback and bug reporting. This is still a nightly feature, so please expect bugs or unfinished features to land (but please keep reporting them!). 🙂
This is great feedback, thank you!
@klint At this moment, that isn't in our roadmap.
@massic80 This is filed as #20661
@tom-james-watson Selecting an inactive tab, should move it out of the inactive section and into it's prior position. If you can reproduce this behaviour, please file a bug, that would be helpful!
This is something I noticed as well: should we disable scroll to position if the last selected tab is now inactive? I'll bring this up with our team to see what the best interaction should be. Thanks for calling it out! |
Thanks for the replies!
I think the answer is to put the inactive tabs at the top of the tab tray, not at the bottom. If the newest tabs are at the bottom then the inactive, and therefore oldest, should be at the top. I still don't understand the motivation for splitting tabs into active and inactive though. Is it to somehow "archive" old tabs? If so, if I want that as a user then I can opt-in to having old tabs auto-closed, no? Personally, if I left a tab open then I want it there as a normal tab. I appreciate this isn't finished, it's just that we have no transparency on why the change is being made or what the final functionality is meant to look like. If we were able to see the requirements and/or motivations then we'd better be able to report bugs and give feedback. |
Thanks for the replies. I agree with the previous comment, as I stated myself in another issue : logically, inactive tabs should be above active tabs. Now, regarding syncing not being in the roadmap and other things: aren't we falling in the same trap as for collections? Last point: there should be a option to not use inactive tabs (and keep as many active tabs as we want as longer as we want it). |
Hi @jonalmeida ! Verified as implemented on the latest Nightly (93.0a1 - 2021-08-13T05:08:25.050265).
Closing the ticket as verified. |
Honestly I don't understand either this "feature"... At least if inactive tabs where just simply put in another tab (next to private and synced) as candidates to be quickly closed it would make more sense... Yet I don't think I would like to use it either... I feel like this feature is to resolve a problem which only exists because Fenix want to create tons of tabs. Not creating tabs when it isn't asked for would have solved it... It pains me that efforts are spend on that and not improving user experience based on what it's been requested for ages and multiple times. Especially when shortcomings push workarounds like this one. 😟 |
I would like to see the initial motivation for adding this feature. For me, a person that opens a lot of tabs, it's basically a daily tab shuffle with no upside whatsoever. From browser standpoint the tabs are inactive anyway (I think), so it doesn't really change anything aside from adding poor UX. |
This will be a section on the tabs tray of tabs that have not been used recently.
We need to set a variable number for what determines how long a tab needs to have existed without activity before it becomes "inactive" - we're starting with 4 days for now and we can alter that as we find a good number.
We should use the
lastAccess
property in the tray list to filter the tabs list into the two sections.Linked JIRA: FNXV2-17122
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: