988541 - Java program does not launch - Evj evolution program

Status: RESOLVED INCOMPLETE

(Core :: General, defect)

Description

[Tom Schneider]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25 (Beta/Release)
Build ID: 20140318183546

Steps to reproduce:

Computer: Mac OS X 10.9.2
Seamonkey: 2.2.5 (latest)
Firefox: 23.0 (Note: I put 'Version' as 23 Branch to match this. May not be the
   right thing to do!)
System Preferences: Java/Security set to Medium.
Adding a security exception does not matter.

go to
http://schneider.ncifcrf.gov/papers/ev/evj/evjava/index.html
with either SeaMonkey or Firefox



Actual results:

The Java program Evj does not launch a window.


Expected results:

A Java window would launch to run Evj.
This WORKS in Safari.

So it appears that SeaMonkey and Firefox are not launching Java programs correctly
even though Safari can do so.

Comment 1

[Tom Schneider]

http://schneider.ncifcrf.gov/papers/ev/evj/evjava/index.html
I upgraded to the latest Java 7 version 75.  I installed the legacy Java ES 6 on my OS X Yosemite version 10.10.1 MacBook Air.
I got the latest version of SeaMonkey User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32
Build identifier: 20150112232400

When I go to the above page the java field is BLANK.

On Safari I got a message and was able to set up the security and it ran.

What is wrong with SeaMonkey?

Comment 2

[Rainer Bielefeld]

None of the contributed hyperlinks (They are all the same <http://schneider.ncifcrf.gov/papers/ev/evj/evjava/index.html> cause error message cause error message "schneider.ncifcrf.gov could not be found. Please check the name and try again.".

No way to reproduce the problem.

Comment 3

[Tom Schneider]

That website is down.  The new location is pointed to by this link:
https://alum.mit.edu/www/toms/papers/ev/evj/evjava/index.html
That should always work.

However, Java has changed and now requires security that I haven't gotten around
to implementing.  So I suppose you could close this bug since I can start a new one
if SeaMonkey doesn't work with the new security.