Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Visually separate user and auto-saved sessions #830

Closed
martixy opened this issue Jul 31, 2021 · 4 comments
Closed

Feature: Visually separate user and auto-saved sessions #830

martixy opened this issue Jul 31, 2021 · 4 comments

Comments

@martixy
Copy link

martixy commented Jul 31, 2021

Is your feature request related to a problem? Please describe.
It's really hard to tell user sessions from auto-saved.

Describe the solution you'd like
Put user sessions and auto-saves in a separate location in the UI.

Describe alternatives you've considered
n/a (Yes I am aware of the existing dropdown, it is not a viable alternative.)

Additional context
I got this extension because it can save tab groups (my favourite new feature), but the UI is very... obstructing.
(I am using the extension in Chrome.)

@skalfate
Copy link

I second this request. ❤️

@sienori
Copy link
Owner

sienori commented Oct 11, 2021

I improved the appearance of tags in autosaved sessions. This makes it easier to distinguish between autosaved sessions.
image

@skalfate
Copy link

skalfate commented Oct 11, 2021

Thank you sienori. That is helpful but what would be even better is a designated section for it as requested. Perhaps you can experiment with it.

The below image is its current layout, maybe it may serve as inspiration for you to play around where a section can fit.

Layout Highlighted

@martixy
Copy link
Author

martixy commented Oct 12, 2021

I suppose the original problem definition is somewhat misleading. The whole issue was, admittedly, created lazily with the most obvious problem and a proposed solution copied from elsewhere.

Here's a better version:

Sessions are both hard to tell apart and hard to navigate.

Keep in mind - even the first part is still difficult. Reading words or parsing symbols is significantly slower than recognizing color. What I mean to say is, color-coding the badges will make it immediately obvious which is which type it is. Better yet, you may save the vertical space and color the background. Size is also a good indicator, and one may learn to distinguish different items at a glance with some practice, provided the differences are major enough. Parsing the symbols comes third on that ladder and reading actual words is at a distant fourth. Of course, people may be color blind, have other visual deficiencies, so combining multiple approaches to increase accessibility is the best solution.

Potentially we could have collapsible sections for each category (which remember their collapsed state - a seemingly obvious detail that bears mentioning).

The current list also has merits - it preserves timing information - which session is before/after another one, which is lost if you split things into sections. However, having the menu is decidedly user unfriendly. It hides information - what types of session types exist and requires more clicks the necessary. A list of all existing session types, along with a toggle for each type (e.g. a checkbox) would resolve each of these issues.

The ideal solution for me would be: Symbol, text and color on the toggles. Only symbol and background color on the sessions themselves.

Lastly, something that might probably be good for a separate feature request, but: Look at the windows/tabs list of a save session - you see the window titles of each saved tab. Now go to the bookmark manager in chrome and select a bookmark. Notice how the address of that bookmark appears next to its title, grayed out. Session buddy does it on hover (but touch inputs do not support hover). For my money, I'd just have it permanently visible.

@martixy martixy closed this as not planned Won't fix, can't repro, duplicate, stale May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants