Dine kommentarer
Known problem. Really this tool is mostly unusable for users who have the option "Continue where i left off" turned on.
This is because of the luck of appropriate API in Chrome itself, to correctly distinguish reopened tabs from new, and normally closed (on Chrome exit) from crashed
Mostly this tool is for a real tabs addicts, and they actually very rarely restart the Chrome, so this is not a huge issue for them.
Yet your suggestion to just give the option to turn off the crashed windows management might help to make it more compatible for your case.
Need to think. It might be quick and easy fix.
This is because of the luck of appropriate API in Chrome itself, to correctly distinguish reopened tabs from new, and normally closed (on Chrome exit) from crashed
Mostly this tool is for a real tabs addicts, and they actually very rarely restart the Chrome, so this is not a huge issue for them.
Yet your suggestion to just give the option to turn off the crashed windows management might help to make it more compatible for your case.
Need to think. It might be quick and easy fix.
Known problem. Really this tool is mostly unusable for users who have the option "Continue where i left off" turned on.
This mostly because of the luck of appropriate API in Chrome itself, for correctly distinguish reopened tabs from new, and normally closed (on Chrome exit) from crashed
Mostly this is tool for a real tabs addicts, and they actually very rarely restart the Chrome, so this is not a huge issue for them.
Through maybe your suggestion to just give the option to turn off the crashed windows management might help to make it more compatible for your case.
Need to think. It might be quick and easy fix.
This mostly because of the luck of appropriate API in Chrome itself, for correctly distinguish reopened tabs from new, and normally closed (on Chrome exit) from crashed
Mostly this is tool for a real tabs addicts, and they actually very rarely restart the Chrome, so this is not a huge issue for them.
Through maybe your suggestion to just give the option to turn off the crashed windows management might help to make it more compatible for your case.
Need to think. It might be quick and easy fix.
Known problem. Really this tool is mostly unusable for users who have the option "Continue where i left off" turned on.
This mostly because of the luck of appropriate API in Chrome itself, for correctly distinguish reopened tabs from new, and normally closed (on Chrome exit) from crashed
Mostly this is tool for a real tabs addicts, and they actually very rarely restart the Chrome, so this is not a huge issue for them.
Through maybe you suggestion to just give the option to turn off the crashed windows management might help to make it more compatible for your case.
Need to think. It might be quick and easy fix.
This mostly because of the luck of appropriate API in Chrome itself, for correctly distinguish reopened tabs from new, and normally closed (on Chrome exit) from crashed
Mostly this is tool for a real tabs addicts, and they actually very rarely restart the Chrome, so this is not a huge issue for them.
Through maybe you suggestion to just give the option to turn off the crashed windows management might help to make it more compatible for your case.
Need to think. It might be quick and easy fix.
That's interesting case. Maybe really worth to give an option to not display crashed windows on restart at all.
I never really exit from Chrome. For me it's always a crash, and after such crash i am rarely want to use Chrome restore feature, as this often will restore several hundreds tabs. But for only few windows, it's really maybe have a lot of sense to just always use Chrome Restore.
And yes, this is not properly fixed... need to open this bug again.
I never really exit from Chrome. For me it's always a crash, and after such crash i am rarely want to use Chrome restore feature, as this often will restore several hundreds tabs. But for only few windows, it's really maybe have a lot of sense to just always use Chrome Restore.
And yes, this is not properly fixed... need to open this bug again.
I am using this already for more then a year and actually never feel the need for multiselect.
Might you share your use cases?
Do you know that it is possible to multiselect tabs in the Chrome Tab Strip?
That's all not to say that i will not plan to implement this feature, i am actually plan to do so. As many people ask.
But it is really very interesting why some people find this so painful, yet i myself, being a pro user of this tool, and using it every day for many times, with hundred of open tabs, never actually feel an urge for such a feature.
Through i often use tabs multiselect in original Chrome Tab Strip (to move them in set) and often consolidate items before delete using Drag & Drop technique that is described in one of the videos in Help section.
Just interesting.
Can you describe what exactly are you doing when it is feels so painful?
Might you share your use cases?
Do you know that it is possible to multiselect tabs in the Chrome Tab Strip?
That's all not to say that i will not plan to implement this feature, i am actually plan to do so. As many people ask.
But it is really very interesting why some people find this so painful, yet i myself, being a pro user of this tool, and using it every day for many times, with hundred of open tabs, never actually feel an urge for such a feature.
Through i often use tabs multiselect in original Chrome Tab Strip (to move them in set) and often consolidate items before delete using Drag & Drop technique that is described in one of the videos in Help section.
Just interesting.
Can you describe what exactly are you doing when it is feels so painful?
Seems all extensions that render self in panel window is affected.
tree still can be scrolled by scroll bar if opened in a regular window, through Clone button. Or by arrows and mouse wheel.
Seems there is no fix in Chrome is expected very soon, as all current Dev builds have this bug, and so even if they will be fixed by Chrome team tomorrow it come to Stable build only in several months.
Meantime maybe will try to find some workaround in extension itself.
For anyone who reading this - please star this Chrome issue:
https://code.google.com/p/chromium/issues/detail?i...
UPDATE: Problem affect only Windows 7. Also the bug is already marked as fixed and is really fixed now in Dev and Canary Chrome builds. But it's a question when it finally will arrive in the Stable chanell.
tree still can be scrolled by scroll bar if opened in a regular window, through Clone button. Or by arrows and mouse wheel.
Seems there is no fix in Chrome is expected very soon, as all current Dev builds have this bug, and so even if they will be fixed by Chrome team tomorrow it come to Stable build only in several months.
Meantime maybe will try to find some workaround in extension itself.
For anyone who reading this - please star this Chrome issue:
https://code.google.com/p/chromium/issues/detail?i...
UPDATE: Problem affect only Windows 7. Also the bug is already marked as fixed and is really fixed now in Dev and Canary Chrome builds. But it's a question when it finally will arrive in the Stable chanell.
Yes, seems only Win7 is mostly affected. Through on Win8 this problem can also be seen - the very bottom of toolbar with the bottons does not react on mouse hover. Yet scroll-bars and buttons actually react on clicks and drags.
Thanks for this info, was useful to know.
Thanks for this info, was useful to know.
Kundesupport af UserEcho
I definitely plan to add multiselect, even without any other reasons it just feels unfinished without it and really can benefit the program in many ways.
But time-frame for this feature is somewhat blurred. Maybe i come to this only at spring or even summer - just too many other things that need to be done and have higher priority, it's not a one week to finish feature unfortunately.