Loss of Java with latest FF 79 upgrade
After installing FF 79, we lost the ability to properly view material that require Java script. We verified that Java script was still enabled - it is. Chrome works perfectly on the same items. This situation created an unknowing error on our part, in that, trying to go back to 78.02, we ran into a compatibility issue with the profiles folder / files. Saving the profiles in 79 stamps them accordingly, and will not allow that folder to be used on 78.02. That unleashed 2 day's worth of struggle to get back to 78.02 with everything we had customized, plus our bookmarks. We found this compatibility issue very hard to crack using the FF help system, but eventually we succeeded by manually creating a "new folder", and copy / pasting all the files, deleting the compatibility.ini. We then invoked this default New Folder and got back to normal. And yes, Java-based items are working normally again. There seems to be no grumbling on the web (at least, as yet) about what we regard as a bug, but we did waste a couple of days on this, and are now carefully "Not now"-ing the update to 79 message, until more info is available and a fix is offered.
All Replies (8)
Note that there is a difference between JavaScript and Java.
If there is a problem with JavaScript then this is usually a problem with a content blocking extension.
If you use extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) that can block content (Adblock Plus, NoScript, Disconnect, Ghostery, Privacy Badger, uBlock Origin) always make sure such extensions do not block content.
- make sure your extensions and filters are updated to the latest version
- https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems
Firefox shows a purple shield instead of a gray shield at the left end of the location/address bar in case Enhanced Tracking Protection is blocking content. You can click shield icon for more detail and possibly disable the protection. You can check the Web Console for messages about blocked content.
You can check the Web Console for messages about blocked content.
- "3-bar" menu button or Tools -> Web Developer
- https://developer.mozilla.org/en-US/Tools/Web_Console
I appreciate your input; thanks! To review: Before the update, all was normal. After the update, Facebook (and other) sites wouldn't load, and there was a reference to, I believe, Javascript, rather than Java. On either the BBC web site or The Guardian news site, a video refused to play, citing lack of Java ( I cannot recall exactly what the error message said) and requesting that I re-enabled it. However, Java was enabled, both before and after. Nothing was done to the Java add-on extension, nor to Ad-Block, Ghostery, or No-Script extensions, and they all seem to operating normally. When we finally succeeded in reloading V 78.02, without doing anything with Java, or anything else, Facebook operated as normal. The news video in question was no longer available, but all videos invoked today operate normally. No-Script is set to allow these sites. Because the restoration of FF 78.02 immediately cured the problem, would not the above history suggest that FF v79 brought the problem about in some way; either directly or indirectly, or because one of the add-ons is incompatible with FF v 79?
Firefox releases has not allowed the (NPAPI) Java Plugin from Oracle to run since the Firefox 52.0 Release and there is no Java extensions.
Why do Java, Silverlight, Adobe Acrobat and other plugins no longer work? article.
Also http://kb.mozillazine.org/JavaScript_is_not_Java as JavaScript was originally going to be called LiveScript which would have helped with users in not confusing the two different things.
You can start Firefox in Safe Mode to check if one of the extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) or if hardware acceleration is causing the problem.
- switch to the DEFAULT theme: "3-bar" menu button or Tools -> Add-ons -> Themes
- do NOT click the "Refresh Firefox" button on the Safe Mode start window
Thanks for the replies! Given the waste of two days trying to get back to a working system, it probably won't be a surprise to know that we are more than reluctant to repeat the performance. That said, there is some more info: I have determined that the version of Java that our W 10 PC has on it is a long out of date 1018 issue. Also that, as mentioned, the 64 bit version of FF has been incompatible with Java for years. When I attempted to find the version from the command line (Java -version) the black report panel simply flashes and disappears. That suggests that it is present, but not functional. There is no sign of Java in any form within our Firefox add-on extensions. So perhaps it is only Javascript that is involved... Does this lend support to the notion that if the loaded version of No Script is incompatible with FF v 79, that it could have interfered with Javascript in some way? It is worth mentioning that four FF extensions, including Ghostery, and No Script both list as having updates available (I was unaware of this until today). I have no idea how to go about discovering whether the latest versions are any more compatible with FF 79 than with FF 78.02. Thanks.
The good news is, browsers do not require Java software to run JavaScript. All the necessary interpreters and compilers come built-in.
It is odd that multiple sites told you JavaScript was disabled but in about:config it was enabled. Hard to explain unless scripts were being blocked by an add-on or the program files were corrupted.
Whatever happened on the last try, I think there is an abundance of suggested diagnostics in this thread if the issue recurs on the next one.
rnjbailey said
Also that, as mentioned, the 64 bit version of FF has been incompatible with Java for years.
It was not incompatible just that only 32-bit Firefox for Windows allowed other Plugins besides Flash and Silverlight to run. Other NPAPI Plugins like Java Plugin did run on the 64-bit Firefox for Linux and Mac. Now only the Flash Player Plugin is allowed to run, with limitations since Fx 69.0.
Okulungisiwe ngu James
rnjbailey said
Does this lend support to the notion that if the loaded version of No Script is incompatible with FF v 79, that it could have interfered with Javascript in some way?
It is worth mentioning that four FF extensions, including Ghostery, and No Script both list as having updates available (I was unaware of this until today). I have no idea how to go about discovering whether the latest versions are any more compatible with FF 79 than with FF 78.02. Thanks.
As far as NoScript goes, that add-on can ruin your day.
I doubt if one version i arrears with NoScript would cause that. But you find out if just update it.
Ghostery can ruin your day, too. And not for being one version behind, but I can't say that for sure. Never used that POS, as I have done with NoScript for many years,but don't any longer. Too high maintenance after Quantum landed, I didn't to deal with the new NoScript User Interface.
And as mentioned Java runs far differently that JavaScript does; not even close to each other, beyond the misconception brought about by the "Java" similarity with the JavaScript name.