Roger Fink wrote:
-------- Original Message --------
Interviewed by CNN on 05/03/2013 12:04, Roger Fink told the world:
FWIW, while the latest java update, 1.7.0.17 appears to work well, it
also knocks out javascript in SeaMonkey 2.15.2, at least that was my
experience (Firefox 18.0.1 was unaffected).
I reverted back to 1.7.0.15.
I don't see how it could "knock out" javascript, since javascript is
embedded in the Gecko engine, and Java is a plug-in. That is, Java only
receives code that has been handed to it by Gecko. If it's Javascript,
Gecko won't hand it to Java. The two technologies (Java and Javascript)
aren't related except by name.
And, by the way, I have just tested Seamonkey with Java 1.7.0.17 on the
ACID3 page (which uses a lot of Javascript) and it passed with no
problems.
http://acid3.acidtests.org/
I understand that the "relationship" between the two is just an
accident of language, or careless use of language, but the sequence of
events was hard to miss and Win7 system restore did what it was
supposed to do. Everything is fine now except that I'm back to the
older version. I posted this because I wanted to see if other people
experienced the same problem.
Seeing that you are using Win7, I wonder if that recent MS Win7 platform
update of Feb 27 could be involved. I read elsewhere of many people
having imaging problems after that update. MS has acknowledged that
some systems are having problems with it, and changed it from Important
to Optional.
Luckily I didn't install it, because I had read here of Jim Taylor's
problem with KB 2670838. Just a thought.... do you use MS "automatic"
updates?
bj
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
