"Page Unresponsive" warning + scrollbars is not work if dragged by mouse

[Vladyslav Volovyk]

UPDATE

Problem is fixed for now.

PLEASE UPGRADE YOUR CHROME to version 32.0.1700.102 (through About dialog)

---------------------------------

After the last Chrome update there is a serious trouble come to every extension (and web page) that is use popup panels to render own content.

Scrollbars stop react on mouse clicks - it's impossible anymore to scroll tree by dragging the scroll thumb by mouse.

And also after the scrollbars will be clicked the "Page Unresponsive" warning will start to appears (through the tree will not be really unresponsive).

Mouse wheel, keyboard arrows, PgUp, PgDwn - all of them still work ok, and can be used to scroll the content.

The bug is in the Chrome itself. It can be reproduced on any popup window - any controls that is placed near the bottom or the right part of the window is not operate and produce "Page Unresponsive" warning.

There is the bug in a Chrome bug database that you can staring, to help notify the developers about this this problem and to draw theirs attention to it.

https://code.google.com/p/chromium/issues/detail?id=335634&thanks=335634&ts=1389985880

Please star it!

I am in a search of a workaround meantime.

Regards,

Vladyslav - The Developer Of Tabs Outliner.

Update:

Some workarounds:

If Tabs Outliner will be opened in a regular Tab (through the Clone button, but note that bottom part of this button is also not react on mouse and produce same warning - need to click on the upper half) then scrollbars in such window can be operated without problems.

The cloned window then can be bookmarked, and after that this bookmark can be used to directly open Tabs Outliner in a regular window.

Update:

One more solution of how to restore scrollbars functionality on the current Stable Channel:

http://superuser.com/questions/704736/cant-use-scrollbars-of-dropdowns-html-select-in-chrome-32/704737#704737

Note that full Chrome restart will be needed after that

[charle...@exeter.ox.ac.uk]

Thanks Vlad! I hope you find a workaround soon, as I use Tabs Outliner a lot, and it's such a shame that it seems "broken" at the moment. Best wishes, Charles.

[Vladyslav Volovyk]

Thanks for support.

The bug is already fixed by Chrome team (it's was actually reported by many other people, and really catch some attention).

Through it is fixed in Canary and Dev builds - need to wait till this fix will propagate to the Stable channel.

But as it's so severe problem, i expect (or at least i hope) that the Chrome team actually will publish it by bypassing the regular

long process (it's basically might take half a year before current Canary version will become Stable and be accessible for all).

Through i am not recommend to switch and use the Canary or Dev builds anyway. I use them myself, to be prepared for changes and problems
(but for some reason never catch this problem, not understand why, maybe i mostly use mouse wheel to scroll), and they are very unstable.

So unstable that TO regularly stop work on them at all, and there was even incident that the database was completely destroyed because of buggy 

update in Canary channel.

Best Regards, Vladyslav.

[Patrick M]

Very encouraged to see how on top of this you are Vlad. Thank you for your excellent work with this extension. I updated Chrome today and I am very inconvenienced by this bug - I imagine it is even more frustrating for you.

I was curious, are there any special precautions we need to take when switching between Chrome build channels to ensure that our TO data is preserved? Or does the extension store our tab data outside of the regular Chrome version? Can I manually back up my TO data?

I glanced through the help file on the extension and didn't see this mentioned anywhere. My apologies if I missed it and waste your time. I've never run a non-stable chrome build before, but if it gets me tabs-outliner back I'm willing to take the risk. The dev-channel page (at http://dev.chromium.org/getting-involved/dev-channel) seems to imply that I would have to uninstall the stable version to get the dev version to run, although it does specifically say canary can be run in parallel to stable. I'm slightly nervous about uninstalling or using canary, so any extra tips on avoiding catastrophe you could provide would be most welcome.

Thank you again,
Patrick

[Vladyslav Volovyk]

Found one simple solution how to restore scrollbars functionality on the current Stable Channel:

It's described there:

http://superuser.com/questions/704736/cant-use-scrollbars-of-dropdowns-html-select-in-chrome-32/704737#704737

Note that full Chrome restart will be needed after that

About backup.

One solution is to use manual backup - expand all nodes then do a Ctrl-S - save as complete HTML.

The resulting file can or be used on it's own. Or hierarchies from it can be dragged back to TO view.

It's actually very handy to do such archive in a file once per several months and just start the tree from scratch.

Automatic solution must regularly backup this folder

C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data\Default\IndexedDB\chrome-extension_eggkanocgddhmamlbiijnphhppkpkmkl_0.indexeddb.leveldb\

and preferable this one:

C:\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data\Default\File System

How to restore from such backups is described there:

https://groups.google.com/d/msg/tabs-outliner-support-group/eKubL9Iw230/wQXOP1m90NoJ

Through i hope very soon release a version which will perform an automatic backups to the Google Drive. And with much simplified process to restore such backups. It will read and import also a saved in HTML trees (through CTRL-S method).

I am highly not recommend to switch to the Dev or Canary channels.

Especially on Dev or Beta. As it is cannot be installed simultaneously with Stable.

Canary can be installed in parallel with current Chrome stable without any problems, and you can do so, just for fun. But note that this version is often have ugly problems.

Best.

Vladyslav

[Vladyslav Volovyk]

One more workaround - open the clone window and bookmark it's link somewhere.
After that use this bookmark to open Tabs Outliner in a regular tab window - it has no such problems.

And one more workaround that found some other user and sent to me on email:

>>>>>>>>>>>>>>

Following your advice, as a temporary workaround, I've disabled TO extension button so that I wouldn't start the buggy pop-up window by accident clicking on extension button (each disabled extension button can be re-enabled via Tools>Extensions menu), and then made a shortcut:

"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" "chrome-extension://eggkanocgddhmamlbiijnphhppkpkmkl/activesessionview.html?type=clone" --new-window

P.S. you can also add this shortcut to Windows 7 taskbar by following instructions here:http://lifehacker.com/5382578/pin-any-item-to-the-windows-7-taskbar

or even more detailed instructions here: http://www.7tutorials.com/how-pin-special-windows-shortcuts-taskbar (read the part about "Move the cursor to the beginning of the line and type the word explorer followed by a space").

Just wanted to share with you - you can share it with other users.

Thanks,

Giedrius
>>>>>>>>>>>>>>>>>>>>>>

[Vladyslav Volovyk]