[thelist] JavaScript open.window CGI-BIN question
Ken Schaefer
ken at adOpenStatic.com
Wed Sep 10 22:00:07 CDT 2003
Javascript is all executed on the client's browser. It has nothing to do
with where the script is located on the server. The *only* way that your
server-side coding might affect this is if it's spitting out javascript that
isn't correct.
Do you get any client-side errors? Have you done a view-source on the client
machine and verified that the script is all valid?
Otherwise, I dunno - some kind of client-side pop-up blocker in action?
Cheers
Ken
----- Original Message -----
From: "Amy Johnson" <amy at rocky-hills.com>
To: <amy at rocky-hills.com>; <thelist at lists.evolt.org>
Sent: Thursday, September 11, 2003 12:50 PM
Subject: RE: [thelist] JavaScript open.window CGI-BIN question
: Oops sorry, I meant window.open() not open.window(). I know the
: JavaScript syntax is ok because it works from the main directory.
:
: Amy
:
:
: > -----Original Message-----
: > From: Amy Johnson [mailto:amy at rocky-hills.com]
: > Sent: Wednesday, September 10, 2003 2:30 PM
: > To: TheList
: > Subject: [thelist] JavaScript open.window CGI-BIN question
: >
: >
: > I have created a series of CGI Perl scripts that generate
: > dynamic HTML
: > pages for a web site. They are sitting in the cgi-bin
: > directory on a
: > UNIX box. My problem is that the dynamically created pages call a
: > JavaScript file in the main directory that uses the open.window
: > command. It all used to work fine. But something happened
: > (maybe on
: > a system level) and now all the JavaScript works EXCEPT the
: > open.window command. It just plain doesn't work (no window pops up)
: > from the cgi-bin Perl scripts. It does however still work from the
: > main directory HTML files. Any ideas about what might be wrong on a
: > system level so I can probe this issue more with the system
: > administrators? I don't know much about JavaScript so I'm
: > clueless as
: > to why this all stopped working.
More information about the thelist
mailing list