Sorry, I didn't mean to not include everyone on my reply...
The reason I need a new window (and I did actually mean _blank), is because this is for a Library portal site which has a limited window view. Our users actually (almost) demand a new window because they don't want to have to hit their back button 20 times to get back to their customized list of electronic Library resources.
And so, if I don't open a new window, then they will complain that they cannot see the site they want to see (because the window is too small) and they have now lost their portal site, which they need to open other sites in order to compare for their research, etc.
I am modifying current open sourced software that's already in place, though not yet in production mode for our users.
Does that help explain why I need it? What would you suggest at this point?
Thanks, Tim
Tim McGeary Senior Library Systems Specialist Lehigh University 610-758-4998 [EMAIL PROTECTED]
Wiggins d Anconia wrote:
I want my web page redirect to open in a new window, as if I were putting "target=_new" in the html of the URL. How can I do that using CGI.pm's redirect? I have this:
print $output->redirect($u)
with $u being the URL I am redirecting, too.
The problem is that the redirect is providing an HTTP header back with
the new location and a result code that instructs the browser to find
the page at the new location, this is working at the protocol level
which has no knowledge of windows, targets, etc. So using 'redirect' is
not likely to get you anywhere at the client level.
Generally I would think your best bet would be to have the link itself use a standard target, which for some reason you seem to be avoiding, reasons? Alternatively you could pass back some javascript for the onLoad handler and have it pop the new redirect in a new window, but the problem I see here is that the browser will have already cleared the window's contents and "loaded" a new page, so the same handler would need to restore the previous contents, which gets real ugly, especially if the referer is POST'ed. I wouldn't even want to think about the nightmares dealing with different versions of browsers + javascript, etc. However if your referer is static and you can guarantee it then it wouldn't be as much of a problem.
http://danconia.org
-- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
