> Our code checks for various browsers and operating systems and handles the
> peculiarities of each as needed.
Oh sure <sarcastic grin>. I live in an environment where there is more
than one browser available, most not in any of the common directories,
and on an operating system / desktop combination where there is no real
concept of a "default browser" (there is a something similar thing,
which everyone ignores). "default" is what you start ... How do you
intend to figure out which browser I use today?
> On my "to do" for today was checking Firefox 1.5 for Macintosh, and sure
> enough it has become the first Macintosh browser to block showDocument.
> Things were simpler in the days that one could count on Java methods
> working.
Java is still working and is not to blame. It is that users got sick and
tired of popups, redirections to their sites, and many other sorts of
massive abuse. So users demand from browser manufacturers to plug the
holes. And once one hole was plugged the spammers and abusers figured
out the next hole, until that was plugged, too.
The only one you have to blame are the abusers.
BTW: Why do you think you have the right to open another browser window
on your users' desktops? Probably your users don't want that you open
another window, and won't want your application that way.
/Thomas

Signature
The comp.lang.java.gui FAQ:
ftp://ftp.cs.uu.nl/pub/NEWS.ANSWERS/computer-lang/java/gui/faq
http://www.uni-giessen.de/faq/archiv/computer-lang.java.gui.faq/
Mickey Segal - 07 Dec 2005 17:14 GMT
> Why do you think you have the right to open another browser window on your
> users' desktops? Probably your users don't want that you open another
> window, and won't want your application that way.
We have the right to open another browser window since the applet is
digitally signed. We display further information on other Web sites such as
articles about a diagnosis being considered. Our users asked for this
content and tell us it is important to them. Displaying it in a frame in
the HTML page with the applet would be very clunky. Replacing the HTML page
running the applet stops the applet. If you are arguing that one should not
use applets for this computationally-intensive material and instead should
use server-based code this would make response time much slower than is
possible with a Java applet.
The showDocument method was put in Java for a good reason. It is too bad
that skuzzy marketers have abused it, but a digitally-signed applet should
be able to get back functionality that was included in Java from the very
early versions.