Twoje komentarze
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 everyone who reading this, please star this Chrome issue:
For anyone who reading this - please star this Chrome issue:https://code.google.com/p/chromium/issues/detail?id=335634&thanks=335634&ts=1389985880
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 everyone who reading this, please star this Chrome issue:
For anyone who reading this - please star this Chrome issue:https://code.google.com/p/chromium/issues/detail?id=335634&thanks=335634&ts=1389985880
thanks for update.
It's looks like it is this problem:
http://tabsoutliner.userecho.com/topic/374370-scro...
there is meantime no workaround rather then using mousewhel or keyboard arrows with PsUp PgDn, or opening the TO in regular Tab by Clone button, working on this.
It's looks like it is this problem:
http://tabsoutliner.userecho.com/topic/374370-scro...
there is meantime no workaround rather then using mousewhel or keyboard arrows with PsUp PgDn, or opening the TO in regular Tab by Clone button, working on this.
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.
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.
scroll still work with mouse wheel
Oh, fuck... just update the Chrome and found the same problem...
Interesting - so you was logged in one Chrome profile on all this computers/devices?
It's very strange incident actually.
I cannot even understand what's happen. If TO operate ok it's seems that it is the Chrome who just reset own profile.
Please on a PC with a Chrome instance on which you had the lost tree enter this url in Chrome:
chrome://version/
look for the Profile Path label.
find this path using the Windows Explorer, but not the full path, but the User Data folder
On my PC the path looks like this:
C:\Users\-UserName-\AppData\Local\Google\Chrome\User Data
Then right click on the User Data folder and select Properties.
after that select the Previous Versions tab
it must look like this:
http://imgur.com/lGZbWbT
select some version before the crash
and Press Copy... to copy it somewhere (do not restore, it's most likely will not help, yet you might try, if you know what are you doing, but Chrome must be logged out from your profile and also shut-downed)
Then, in place where are you restore this backup check this folder User Data and please tell me how many inside folders with the names like Profile 1, Profile 4 .....
If you will find no such folders then just enter to Default subfolder and send me the content of File System subfolder inside User Data\Default folder (to vladyslav.volovyk@gmail.com) - i will restore your tree in form of HTML page and will send it back. If Profile 1, Profile X folders available - you need to do the same with all of them.
For future please take note that it is possible to save TO tree to separate HTML file, by expanding all nodes and pressing Ctrl-S.
Best.
It's very strange incident actually.
I cannot even understand what's happen. If TO operate ok it's seems that it is the Chrome who just reset own profile.
Please on a PC with a Chrome instance on which you had the lost tree enter this url in Chrome:
chrome://version/
look for the Profile Path label.
find this path using the Windows Explorer, but not the full path, but the User Data folder
On my PC the path looks like this:
C:\Users\-UserName-\AppData\Local\Google\Chrome\User Data
Then right click on the User Data folder and select Properties.
after that select the Previous Versions tab
it must look like this:
http://imgur.com/lGZbWbT
select some version before the crash
and Press Copy... to copy it somewhere (do not restore, it's most likely will not help, yet you might try, if you know what are you doing, but Chrome must be logged out from your profile and also shut-downed)
Then, in place where are you restore this backup check this folder User Data and please tell me how many inside folders with the names like Profile 1, Profile 4 .....
If you will find no such folders then just enter to Default subfolder and send me the content of File System subfolder inside User Data\Default folder (to vladyslav.volovyk@gmail.com) - i will restore your tree in form of HTML page and will send it back. If Profile 1, Profile X folders available - you need to do the same with all of them.
For future please take note that it is possible to save TO tree to separate HTML file, by expanding all nodes and pressing Ctrl-S.
Best.
Not a top priority, but yes, it will be cool to have such feature.
Worth to note that that this can even be done by separate extension. Which will create own, always attached to the Chrome side panel, or the native sidebar, if this is really possible, and then open Tabs Outliner main view in this panel - it's easily possible as the Tabs Outliner View is just the regular web page with an url, and so it can be opened in a regular tab or a frame (for example it is the way how cloned views created in regular tabs, by using the Clone button)
This extension will also be able also to serve other pages in such a sidebar - very cool idea.
If some web developer reading this - consider to implement such an extension. It will be utilized then by many other extensions.
Maybe it is even already created.... the idea is very cool, need to investigate.
Worth to note that that this can even be done by separate extension. Which will create own, always attached to the Chrome side panel, or the native sidebar, if this is really possible, and then open Tabs Outliner main view in this panel - it's easily possible as the Tabs Outliner View is just the regular web page with an url, and so it can be opened in a regular tab or a frame (for example it is the way how cloned views created in regular tabs, by using the Clone button)
This extension will also be able also to serve other pages in such a sidebar - very cool idea.
If some web developer reading this - consider to implement such an extension. It will be utilized then by many other extensions.
Maybe it is even already created.... the idea is very cool, need to investigate.
As help in Tabs Outliner explain Group is just a saved window. When it's first created by dragging a blue button. Then it can be of course activate, and will become a normal window for some time.
Interesting, on Windows and Ubunta it's definitely works for me as you describe in preferred behavior, maybe this is something Mac specific, need to investigate.
Customer support service by UserEcho
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...