Skip to content
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.

Add inactive tabs tray group #20349

Closed
jonalmeida opened this issue Jul 13, 2021 · 15 comments
Closed

Add inactive tabs tray group #20349

jonalmeida opened this issue Jul 13, 2021 · 15 comments
Assignees
Labels
eng:qa:verified QA Verified feature request 🌟 New functionality and improvements Feature:Tabs
Milestone

Comments

@jonalmeida
Copy link
Contributor

jonalmeida commented Jul 13, 2021

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

@Mugurell
Copy link
Contributor

Created #20507 for the telemetry.

jonalmeida added a commit to jonalmeida/fenix that referenced this issue Jul 29, 2021
jonalmeida added a commit to jonalmeida/fenix that referenced this issue Jul 29, 2021
jonalmeida added a commit to jonalmeida/fenix that referenced this issue Jul 29, 2021
jonalmeida added a commit to jonalmeida/fenix that referenced this issue Jul 29, 2021
jonalmeida added a commit to jonalmeida/fenix that referenced this issue Jul 29, 2021
jonalmeida added a commit to jonalmeida/fenix that referenced this issue Jul 29, 2021
jonalmeida added a commit to jonalmeida/fenix that referenced this issue Jul 30, 2021
jonalmeida added a commit to jonalmeida/fenix that referenced this issue Jul 30, 2021
jonalmeida added a commit to jonalmeida/fenix that referenced this issue Jul 30, 2021
jonalmeida added a commit to jonalmeida/fenix that referenced this issue Jul 30, 2021
@jonalmeida jonalmeida removed the needs:triage Issue needs triage label Jul 30, 2021
jonalmeida added a commit to jonalmeida/fenix that referenced this issue Jul 30, 2021
@klint
Copy link

klint commented Aug 2, 2021

Could the inactive tabs feature be deactivated in the settings?
Because there is a great loss of information in the inactive tabs (no screenshots and shorter site descriptions), information which would actually be needed more for inactive tabs (inactive tabs being older, memory may be failing and more information could help).
This is suddenly breaking the way I'm using the tab tray (as kind of a "read later" list, with plenty of tabs).
[edit]: the loss of information happens both in grid and list modes of the tab tray (either less screenshot or less site description)
Thanks

@klint
Copy link

klint commented Aug 3, 2021

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.

@ericonr
Copy link

ericonr commented Aug 3, 2021

Something in the implementation here reset the setting to 30 days and is killing tabs for a bunch of folks: #20629

@ericonr
Copy link

ericonr commented Aug 3, 2021

@ericonr
Copy link

ericonr commented Aug 3, 2021

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.

@massic80
Copy link

massic80 commented Aug 4, 2021

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.

@tom-james-watson
Copy link

tom-james-watson commented Aug 4, 2021

I don't understand the motivation for this feature at all.

There are several problems as it currently stands:

  • "Reactivating" a tab now moves it out of its tab order.
  • The tab tray shows inactive tabs at the bottom. If you have a lot of inactive tabs, you can't even see your active tabs without having to scroll up every time, which is awful UX.
  • Inactive tabs can't be swiped to close them.
  • Inactive tabs don't have screenshots.
  • Most importantly, this does not seem like a useful feature. Why the arbitrary distinction between active and inactive? What exactly is the desired outcome here? This doesn't fit any mental model I have as a user and doesn't seem to help me in any way.

It doesn't seem like a very well thought through change. Was any UX research done on this?

@WesleyAC
Copy link

WesleyAC commented Aug 5, 2021

I filed #20684 for adding an option to disable this feature.

@jonalmeida jonalmeida added this to the 92 milestone Aug 5, 2021
@jonalmeida
Copy link
Contributor Author

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!). 🙂

Because there is a great loss of information in the inactive tabs (no screenshots and shorter site descriptions), information which would actually be needed more for inactive tabs (inactive tabs being older, memory may be failing and more information could help).

This is great feedback, thank you!

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.

@klint At this moment, that isn't in our roadmap.

I changed its value from the options and reverted it to "close manually" and the tabs have been wiped away anyway.

@massic80 This is filed as #20661

"Reactivating" a tab now moves it out of its tab order.

@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!

The tab tray shows inactive tabs at the bottom. If you have a lot of inactive tabs, you can't even see your active tabs without having to scroll up every time, which is awful UX.

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!

@tom-james-watson
Copy link

tom-james-watson commented Aug 5, 2021

Thanks for the replies!

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!

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.

@klint
Copy link

klint commented Aug 5, 2021

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?
Collections are not synced (and I'm not using them for this reason) and it is a feature whose purpose is not understood, even by the active users community (daredevils like us using nightlies!).

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).
No more automatic deletion of info, please. Even not on nightlies 😉.
Thanks.

@SoftVision-LorandJanos
Copy link

Hi @jonalmeida ! Verified as implemented on the latest Nightly (93.0a1 - 2021-08-13T05:08:25.050265).
Devices used:

  • Samsung Galaxy Tab S3 (Android 9).
  • Huawei P30 (Android 10).
  • Xiaomi Redmi 11 Lite (Android 11).

Closing the ticket as verified.

@Matth7878
Copy link

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. 😟
Some examples : top sites and collections improvement, better access to bookmarks / history, homepage, add-ons, and so on...

@albertmoravec
Copy link

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
eng:qa:verified QA Verified feature request 🌟 New functionality and improvements Feature:Tabs
Projects
None yet
Development

No branches or pull requests

10 participants