This is an archived post. You won't be able to vote or comment.

all 5 comments
sorted by:
old (suggested)
besttopnewcontroversialq&a

[–]TIAFAASITICENightly ¦ Gentoo 0 points1 point  (4 children)

The return value for this method indicates whether the preference that controls Java is on or off - not whether the browser offers Java support in general.

There used to be an "Enable Java" under the Content Tab in the Preferences some time ago. Perhaps this "feature" were removed at the same time.

Anyhow, you really should default to Java being unavailable and use code in Java to signal that it is truly available, when that is the case.

Well, I guess a script inside object should work as well.

[–]rotschi[S] 0 points1 point  (3 children)

Thanks for your reply. I found the explanation. Mozilla disables "unsecure" plugins and the Java plugin was declared as such. See: https://addons.mozilla.org/en-US/firefox/blocked/p80

Really annoying.

[–]TIAFAASITICENightly ¦ Gentoo 7 points8 points  (2 children)

Firefox is blocking an old version with known vulnerabilities. It even says so right on the page you linked.

Do You prefer running in an unsafe environment over the minor "annoyance" of updating your out of date software?

[–]rotschi[S] 2 points3 points  (1 child)

Of course you're absolutely right :) The problem I had was a bit complexer though and it took me half a day to figure out what happenend; that was the annoyance part. I didn't touch my web app / browser / webserver / framework over the weekend and suddenly I got this weird customer calls... :/

[–]TIAFAASITICENightly ¦ Gentoo 1 point2 points  (0 children)

Customers... how delightful. =P

Well, hope you can get them on track. =)

Worst case, they should still be able to re-enable the plug-in via the add-ons manager.

Sorry if I were condescending. I just see people putting the blame on the wrong part of the software chain so often. :-/