You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because this conflicts with things like OneTab, this means I have a couple of saved "pages" that I made of different sections of my OneTab. However, that's led to just a bunch of "OneTab - Shared Tabs" that I can't distinguish from each other unless I open them.
Is there a way to retitle the tab or give it a nickname, the same way you could if it were a normal bookmark? Or even just toss a field in there for contextual info so if I hover, I can see that I've added, idk, "Linguistics" or "Layout code" or whatever it was I was working on?
This comes in handy with a lot of use cases; if someone's saving multiple tabs from the same site in any instance, it can end up all looking the same.
Definitely let me know if this is something there's already a workaround for that I'm just not seeing!
The text was updated successfully, but these errors were encountered:
I'm not aware of this being part of the extension's featureset, and I doubt it will be in the future. Your best bet is probably to try to find another independent extension that does this specific part, such as these:
Because this conflicts with things like OneTab, this means I have a couple of saved "pages" that I made of different sections of my OneTab. However, that's led to just a bunch of "OneTab - Shared Tabs" that I can't distinguish from each other unless I open them.
Is there a way to retitle the tab or give it a nickname, the same way you could if it were a normal bookmark? Or even just toss a field in there for contextual info so if I hover, I can see that I've added, idk, "Linguistics" or "Layout code" or whatever it was I was working on?
This comes in handy with a lot of use cases; if someone's saving multiple tabs from the same site in any instance, it can end up all looking the same.
Definitely let me know if this is something there's already a workaround for that I'm just not seeing!
The text was updated successfully, but these errors were encountered: