- General
-
Bugs
Tabs Outliner window getting out of sync with browser sync
Hi,
I'm having some issues with your extension. Sometimes a new tab stays as "New Tab" in the outliner window even if i've browsed somewhere in it. This seems to happen only with some websites. What i'm doing:
1. Open new tab with CTRL+T
2. Start typing an url ("reddit" for example)
3. Press enter when autocompletion pops up
4. Site loads, but the outliner entry stays as "New Tab" and gets stuck as it. Clicking on it in the outline doesn't focus the tab in the browser window.
It seems to only happen to some websites/urls. It seems that if i instead of pressing enter in step 3 press CTRL+A (goes to the start of the address bar in my OS) then press enter, it works.
I see a lot of errors in the console for the background page for the extension like this:
ERROR Cannot find tab - setActiveTab 550 389 background.js:47
ERROR############## Cannot find tab550 in this.treeModel 550
Object {active: true, highlighted: true, id: 550, incognito: false, index: 7…}
[e, Kb: e, yb: function, findActiveWindow: function, X: function, getAllCollapsedNodes: function…]
background.js:80
Using:
Google Chrome Version 26.0.1410.43
I had some other extensions installed but i've deactivated them but it doesn't seem to help.
Solution
I deleted my chrome cache and config and it seems to have solved itself.. weird.
> I see a lot of errors in the console for the background page for the extension
Ignore them please, most of them is not real errors
Must be fixed of course to not produce the junk in the console, this is already done in next major release, which is not released meantime.
As for tabs that stuck - that's really interesting, never saw such behavior on my pc, and it was never reported before. if you find a way to surely reproduce this please let me know.
With latest Chrome update start to see this problem myself, seems that this is something new that was introduced with Chrome v26, yet cannot understand meantime how to reproduce this bug surely.
Any ideas how to reproduce this bug appreciated. Yet i will catch it in the end anyway : )
Well, i have no idea how to recreate it but it's starting to happen again.. :(
Good luck in fixing it, great job on the extension so far :)
I have go exactly the same problem. It happens not with all addresses, but even when you go to "good" address and then type new address which is not working, it is opened in chrome normally like it should but in outliner ther is a title with this previous "good" address website. If you click on it nothing happens. Sometimes when I angry I turn of outliner and browse for sometime and again turn it back on again, I have few New Tab branches, which of course do not exist.
Closing and open TO window does nothing in terms of recreating the tree. You need to disable->enable it in Settings\Extensions, or on this page chrome://extensions (but don' press the trash icon, this will uninstall and delete all data) if you want to do so.
Btw clearing cache or cookies does not solve a problem. Did not do anything with config though
It is look like some new bug in Chrome v26. I see that the users of some other similar extensions now start to report very similar problems in theirs support groups.
The exact case of how this happens is still unknown for me, yet i saw this problem several times already .
Problem is detected and fix/workaround will be released soon (i hope - today). This is actually a Chrome v26 bug, Chrome extensions API start send inconsistent events in some cases.
Yet of course it is impractical to wait till the Chrome team will fix this (if they will be bothered at all, some serious bugs that i report to them was ignored, even despite they are regressions). So i will release a workaround on my own.
Problem is detected and fix/workaround will be released soon (i hope - today). This is actually a Chrome v26 bug, Chrome extensions API start send inconsistent events in some cases.
Yet of course it is impractical to wait till the Chrome team will fix this (if they will be bothered at all, some serious bugs that i report to them was ignored, even despite they are regressions). So i will release a workaround on my own.
UPDATE Fixed in v0.4.55 - wait till your copy will be update or force update by entering the developer mode in extensions list and pressing "Update Extensions Now" button.
Problem is detected and fix/workaround will be released soon (i hope - today). This is actually a Chrome v26 bug, Chrome extensions API start send inconsistent events in some cases.
Yet of course it is impractical to wait till the Chrome team will fix this (if they will be bothered at all, some serious bugs that i report to them was ignored, even despite they are regressions). So i will release a workaround on my own.
UPDATE Fixed in v0.4.55 - wait till your copy will be update or force update by entering the developer mode in the extensions list and pressing "Update Extensions Now" button.
Service d'assistance aux clients par UserEcho
Problem is detected and fix/workaround will be released soon (i hope - today). This is actually a Chrome v26 bug, Chrome extensions API start send inconsistent events in some cases.
Yet of course it is impractical to wait till the Chrome team will fix this (if they will be bothered at all, some serious bugs that i report to them was ignored, even despite they are regressions). So i will release a workaround on my own.
UPDATE Fixed in v0.4.55 - wait till your copy will be update or force update by entering the developer mode in the extensions list and pressing "Update Extensions Now" button.