In article <bodo0n$sfb$1$8300dec7@news.demon.co.uk>,
Richard@litotes.demon.co.uk enlightened us with...[color=blue]
>
> As Grant said, your original test page wasn't going to work because it
> was assigning a string instead of a function. But testing:-
>
> <html>
> <head>
> <title></title>
> <script>
> function UnLoaded(){alert('bye bye');}
> window.onunload=UnLoaded;
> </script>
> </head>
> <body>
> test
> </body>
> </html>
>
> - worked with (Windows) Netscape 7.00 & 7.02 both from the local file
> system and over an HTTP server.
>[/color]
Not on ours.
I have 2 users who test for me, and they have 7.0, and this gave the
same error.
I wonder if it's something in their settings...
Neither has a user.js file that I could find. I know people can turn off
onunload with a setting in that file, but neither of them have that.
[color=blue]
> If all else fails, have you considered branching on
> window.addEventListener and using that for onunload if available?
>[/color]
I already did a workaround, but it was icky. I put the function call in
the onunload event of each body tag of every damn page (thank goodness
for dreamweaver templates!).
addeventlistener for onunload did the same error for their browsers.
This wouldn't be that big of a deal if we didn't have a ton of Netscape
users. *sigh*
-------------------------------------------------
~kaeli~
Jesus saves, Allah protects, and Cthulhu
thinks you'd make a nice sandwich.
http://www.ipwebdesign.net/wildAtHeart http://www.ipwebdesign.net/kaelisSpace
-------------------------------------------------