[Ext] userChrome.js [support discontinued]

[jfty.009260]

@Alice0775: Your External Editor script for Stylish (link: http://forums.mozillazine.org/viewtopic.php?p=2772333) doesn't work for me consistently. When I open the script manager and edit 1 script, it works flawlessly but when I exit from editing that script and pick another script to edit, the button won't do anything. The script manager requires re-opening before the script would work again. Could you please help me? I'm using Fx 2.0.0.13 btw. Thanks.

[Alice0775]

@Alice0775: Your External Editor script for Stylish (link: http://forums.mozillazine.org/viewtopic.php?p=2772333) doesn't work for me consistently. When I open the script manager and edit 1 script, it works flawlessly but when I exit from editing that script and pick another script to edit, the button won't do anything. The script manager requires re-opening before the script would work again. Could you please help me? I'm using Fx 2.0.0.13 btw. Thanks.

Pls try this.
http://space.geocities.jp/alice0775/STO ... edit.uc.js

[jfty.009260]

It's still not working for me. However, your other script (@ http://space.geocities.jp/alice0775/STO ... itor.uc.js) for editing form fields/text boxes with an external editor from the context menu (which is like It's All Text! without the fading in/out button) works flawlessly for me.

[Alice0775]

It's still not working for me. However, your other script (@ http://space.geocities.jp/alice0775/STO ... itor.uc.js) for editing form fields/text boxes with an external editor from the context menu (which is like It's All Text! without the fading in/out button) works flawlessly for me.

I don't know what is wrong.
However, there may be the cause of the problem on expansions or a theme.

[zeniko]

Alice0775: Please try dropping the WindowHook hack, with userChrome.js 0.8 it's no longer needed (see this post). In fact, you can even stop passing <code>window</code> around, as now <code>window</code>, <code>document</code>, etc. will all refer to the objects in the targeted window.

jfty.009260: If a script doesn't work, always make sure to check the Error Console first. To make sure that you actually see the errors, I recommend installing the Console² extension (otherwise you'd have to meddle around in about:config).

[jfty.009260]

Alice0775: Please try dropping the WindowHook hack, with userChrome.js 0.8 it's no longer needed (see this post). In fact, you can even stop passing <code>window</code> around, as now <code>window</code>, <code>document</code>, etc. will all refer to the objects in the targeted window.

jfty.009260: If a script doesn't work, always make sure to check the Error Console first. To make sure that you actually see the errors, I recommend installing the Console² extension (otherwise you'd have to meddle around in about:config).

There was nothing in the error console that referred to the external editor script. This, however, looks suspicious:

Error: document.loadOverlay is not a function
Source File:userChrome.js
Line: 30

Now what?

[zeniko]

Now what?

What'd'ya think? Roll up your sleeves and continue debugging...

This might be a good moment to get some basic JavaScript knowledge and read a debugging tutorial (in case this stuff is new for you). And when you can't solve the issue even when being knowledgeable, come back and then please post enough context so that somebody more experienced doesn't have to be psychic in order to help you.

Good hunting!

[zeniko]

... and since I've decided to close down this thread, please create new threads in the Extension Development forum for your new questions. Cheers!

[LIMPET235]

Locking as per zeniko's request.