No page loaded error

18 views
Skip to first unread message

gior...@gmail.com

unread,
Jun 9, 2018, 3:20:47 PM6/9/18
to Color That Site!

This is the errore I get on every page I load, this happened only a few days ago. I am using ESR Firefox 52.8.1 and "color that site" was working well until now. I don't know how to diagnosticate the problem, can you help me?
Message has been deleted

thierry...@gmail.com

unread,
Jun 13, 2018, 4:40:01 AM6/13/18
to Color That Site!
I have the same error with Firefox ESR 52.8.0 and 52.8.1, but going back to Firefox ESR 52.7.4 then CTS! 0.17 works again, this means there have been some changes in Firefox ESR 52.8.0 which prevent CTS! 0.17 from getting information about the loaded page...

Inside ColourT...@einspeiser.de.
xpi there is an archive chrome/ColourThatSite.jar which contains file ff-sidebar_stylelist.js in which there is

    if (mainWindow.gBrowser.contentDocument && mainWindow.gBrowser.contentDocument.location
        && mainWindow.gBrowser.contentDocument.location.href)
        url=mainWindow.gBrowser.contentDocument.location.href;

which may not work any more, causing `url' to be empty and the following part of the same file to select "No page"?

        if (enabledStylesInScope==0)
            if ((url!="") && (!url.match(/^about:/) || (url=="about:home")))
                get("deckGoBtn").selectedIndex=0;//Go!
            else
                get("deckGoBtn").selectedIndex=2;//No Page
        else
            get("deckGoBtn").selectedIndex=1;//New Style

Michael

unread,
Jun 13, 2018, 4:45:29 AM6/13/18
to Color That Site!
Thanks for the debugging work, Thierry! :-)

I am currently a bit busy in other projects & work. But I will try to have a look at the changes from 8.0 to 8.1. If there's an easy way to fix this, I will try to put up a fixed version. My current guess is, that access to contentDocument is somehow limited. (Didn't throw an error though as it seems, so it hasn't been removed)

If anyone else has ideas about this, please continue to post.

thierry...@gmail.com

unread,
Jun 13, 2018, 5:09:43 AM6/13/18
to Color That Site!
I am not certain that the change is only in the FF code, it may be reflected also in the profile: I have just found out that using FF ESR 52.7.4 with my latest profile from FF ESR 52.8.1 also prevents CTS! from accessing the URL.
Using FF ESR 52.7.4 with an older profile that dated from FF ESR 52.0.1 allows CTS! to work.

Michael

unread,
Jun 14, 2018, 4:03:20 AM6/14/18
to Color That Site!
Hi Thierry,
I made a little test with Firefox ESR 52.8.1.

I used the 32-Bit version for that.

First I re-used an older profile which I used for developing.  -> Works.

Then I created a new profile, installed the add-on. -> Works.
(I did not verify the addon in-depth though.)

Do you use the 64-Bit version?
So it might relate to the profile. Maybe it collides with another add-on?

Michael

gior...@gmail.com

unread,
Jun 18, 2018, 5:57:13 AM6/18/18
to Color That Site!
Hi,
I tried to rename (bak) the folder of color that site from the user profile folder and I removed and reinstalled the addon. Now it is working! I don't know what happened, maybe firefox update messed up something.

thierry...@gmail.com

unread,
Jun 18, 2018, 7:21:16 AM6/18/18
to Color That Site!
I am using FF ESR 64-bit version on Linux Mint, and it does seem related to the profile (see my answer to gio... below)

thierry...@gmail.com

unread,
Jun 18, 2018, 7:26:56 AM6/18/18
to Color That Site!
Thanks a lot!
Even in FF ESR 52.7.4 CTS! had stopped working for me, and now back in FF ESR 52.8.1, uninstalling CTS! and reinstalling it has allowed it to work again.

This may come from the following difference in the profile: in file extensions.ini there is now an added line under "[MultiprocessIncompatibleExtensions]"
Extension0=ColourT...@einspeiser.de

Reply all
Reply to author
Forward
0 new messages