Its always a challenge!
I've been thinking to do a video "quick start guide" with a voice over and subtitles for TO, but if you go and change default behaviours... then that video will be out of date really quickly!
In my experience with usability its important to try and find something that will make sense and work for the 90% people without documentation.
I guess a question about my input is, "Am I the 10%?" and should you be telling me to go a play in the traffic? :D
I guess I'm starting to become an advanced user of TO now, and like you said, the adaptation took some time for me. I just had to basically try everything and read the docs three times to get it properly.
I'd be happy to help wherever I can to try and find solutions that work for the 90% which I think most of TO does already.
I guess because its simple yet powerful and works a certain way today, perhaps a compromise it to make more options for people to choose a use case that works for them.
Perhaps even starting people on the settings page, so they can choose how it works for them and also train them with basic concepts through their own choices...
What is very clear to me, the basic core features are very powerful and I love it. Its changed to the way I'm working, productivity is up and Chrome resource utilisation is down. :) :) Having 100+ tabs open can be such a distraction!
Thanks Vladyslav, I guess what I'm getting at, it would be very cool option if the protection would be inherited from the parent node.
Related: "Continue where I left off" feature works nicely in Chrome, but it doesn't seem to play well with TO right now? So turning it off kind of makes nodes vulnerable. I have to pay special attention to save+close tabs via TO before I can exit Chrome.
OK, having re-read the documentation again and played more with the extension, I'm happy to report that it appears the concept/code already exists to handle tabs/windows being closed via normal Chrome methods, like CTRL+W or window/tab X button AND being saved/persisted by TO.
The caveat today is, one needs to have customised the window/tab node in the tree. Customised/Persisted nodes +/- control will turn green, then the node doesn't care how you close it, it persists... awesome. I think the docs refer to this as "green tick".
I guess what would be useful, as mentioned in this topic:
Same sub-optimal auto-scroll is experienced when a tab is duplicated with ctrl+click or middle mouse click.
Thanks for the info, some things to note about pinned tabs
A bit more testing, if I have Chrome setting as: "Open the new tab page" and ensure I close all windows/tabs with TO first, then exit Chrome, this seems to work as expected. However in this case, I only have a blank tab when I launch Chrome again. This feels like I'm loosing basic functionality.
I just re-tested but with setting "Open the new tab page" instead of "Continue where I left off" and the same issue occurs.
Furthermore, it would seem for non-saved items, the same issue occurs. i.e. If I just have a new window open and then normally Exit Chrome, TO marks the new window in the list as crashed when Chrome starts next time.
I also just noted the same behaviour as in the video happens when focusing a window that is a the bottom of the list.
Perhaps, lets see what Vladyslav says?
Small clarification from my side, I expected a tab to be saved when I used CTRL+W, when it was already part of a saved window/group.
My reaction went something like this when I realised this wasn't possible (yet)
I think using the clone window option is good, however, I do think the logic behind the auto-scroll to focus could be tweaked for usability.
In this video you can see a slightly sub-optimal usability experience when I create a new window.
I've not thought about how to resolve this, but at least you have the video for reference.
Служба підтримки клієнтів працює на UserEcho