> Maybe this behaviour stems from the many security improvements made in SP2
> to foil people who put advertising popups on websites.
We ran into some other problems using showDocument (www.segal.org/java/pop/)
and ended up using the fact that our applet was digitally signed to open new
browser windows on Internet Explorer on Windows XP using:
Runtime.getRuntime().exec("\"C:\\Program Files\\Internet
Explorer\\IEXPLORE.EXE\" " + url);
In other environments one can use the straightforward:
getAppletContext().showDocument(url, "_blank");
I suspect that this may be the case, but one has to wonder: I doubt the
behaviour we see was the intent (it makes no sense - the user has to
request the save that causes the problem.)
The point here is that the problem is *not* the pop up window - the
problem is with a save button from within that pop up window.
The security of the pop up I can cope with - a user has to allow the
site to pop up a window: That's fine - it's their perrogative.
The problem is that the popped up window is then just broken, which
make no sense.
We may have to move to using a signed applet instead of an unsigned one
to get round this bug. Gah. works great in firefox, and opera, and
netscape, and probably konqueror too ... (hmm - maybe not.)
porter - 16 Nov 2005 16:49 GMT
I know that with groups I sometimes get frustrated that a posting
contains a question, but no answer, so as we've now discovered the
cause of this (and a workaround) I'm posting in a solution to my own
question:
First - It is an IE6 XP sp2 bug. Period.
Our page launched from the java showDocument call contained a frameset.
In one of the frames there are several buttons (Save file X, Save file
Y etc.)
If any of the 'save' buttons in the page is set so that URL <href>'s
target attribute is explicitly set to "_top", they all work (even those
with the attribute "_self")
If they are all set as "_self" then the bug manifests itself, but only
if the browser window is launched from a java showDocument call. If you
create the page through other means you don't see the problem.
..... in the words of Homer Simpson .........
"Doh!"
Thanks to all...
J.
Mickey Segal - 16 Nov 2005 17:56 GMT
> We may have to move to using a signed applet instead of an unsigned one
> to get round this bug. Gah. works great in firefox, and opera, and
> netscape, and probably konqueror too ... (hmm - maybe not.)
I discovered yesterday that treatment of popups in Firefox 1.5 is changed to
now block showDocument. We now use the Runtime.getRuntime().exec approach
in Firefox as we do for Internet Explorer. Be sure to test in Firefox 1.5
(currently in beta).