Forbidden or allowed: no java applet in SpaceWeather

[kurtking]

In Firefox 3.0.11 Java and Javascript are both allowed. In NoScript 1.9.3.3 Spaceweather.com
http://spaceweather.com/java/archive.html had been allowed. But this time whether allowed or not, the java applet is missing. The page says, "If you had a Java-enabled browser you would see an applet here." (Curiously, that text I had to manually type because the underlying content wasn't copyable.)

Code: Select all

<APPLET name="SunSpots" code="PlotDemo" width=400 height=250
    codebase="."
    alt="If you had a java-enabled browser, you would see an applet here.">
    <PARAM name=foreground value="444444">
    <PARAM name=background value="ffffff">
</APPLET>

Another curiosity is when I forbid spaceweather.com the NoScript status line doesn't show.

Two other curiosities I can't reproduce: 1) once spaceweather.com was once Italicized in the whitelist. and 2) once I saw a NoScript object placeholder for the blocked applet - but after I clicked it and got the confirmation message the placeholder went away and no applet appeared.

I tried disabling NoScript and the problem with this site remained.

For comparison, in IE 8 the applet works normally, and I know it worked normally at some time in the recent past with FF before NoScript (and, maybe, after).

Does anyone have an idea about what's going on here?

Thanks,
Kurt

Edited with the applet code.

[Tom T.]

In Firefox 3.0.11 Java and Javascript are both allowed. In NoScript 1.9.3.3 Spaceweather.com
http://spaceweather.com/java/archive.html had been allowed. But this time whether allowed or not, the java applet is missing. The page says, "If you had a Java-enabled browser you would see an applet here." (Curiously, that text I had to manually type because the underlying content wasn't copyable.)

Firefox > Tools > Options > Content > Enable Java. Checked?

Another curiosity is when I forbid spaceweather.com the NoScript status line doesn't show.

I couldn't reproduce this, but see the version difference and reference to troubleshooting below.

Two other curiosities I can't reproduce: 1) once spaceweather.com was once Italicized in the whitelist.

.
Italicized means that it is *temporarily* allowed for that session only. When you close the browser, it is removed from whitelist.

and 2) once I saw a NoScript object placeholder for the blocked applet - but after I clicked it and got the confirmation message the placeholder went away and no applet appeared.

See above. If your previous session had been only a "temporarily allow", then JavaScript would not be allowed at the next visit.

I tried disabling NoScript and the problem with this site remained.

Then it sounds like a Java issue rather than a NoScript issue. Do you have the latest Java, or does Java work properly at other sites? Test: (takes about 60 seconds to complete)
http://www.java.com/en/download/help/testvm.xml
If you don't see the little dancing logo in about a minute, there's a Java issue. (make sure Java and Javascript from java.com and sun.com are allowed)

For comparison, in IE 8 the applet works normally, and I know it worked normally at some time in the recent past with FF before NoScript (and, maybe, after).

I use Firefox 2.20 for personal reasons, so what my browser sees at the site might be different from yours. Actrually, I can get the applet to run just by clicking the NoScript block-logo and OK, even without allowing scripting from the site.

Does anyone have an idea about what's going on here?

Other than making sure that Java is enabled in *Firefox* as well as in NoScript, and that the Java test is succcesful, you might try the latest development build of NoScript, and also the General Troubleshooting instructions. Extension conflicts, for example, are a common cause of problems. The latter will help find or rule those out, among other possibilities.

Let us know.

[Tom T.]

kurtking, it's been almost a week, and we haven't heard back from you. If the issue is resolved, please let us know. If life has just gotten in the way of attending to this matter, as it often does, that's OK too. Just let us know if you are still interested in diagnosing and solving the issue, so we know whether to keep this topic open or mark it as closed. Thanks.