Meaning of Netscape 7.0 Error Messages

[peterinwa]

Note: Just before posting this I solved my problem (see the P.S.) but I am still curious about a reference...

Is there a reference somewhere? My HTML/JavaScript/Frames pages run well on other browsers, even Netscape 4.7, but crash with 7.0.

It happens when I reload the page which in turn recreates itself with JavaScript. Here's the reload part:

// Function to change food list
function changeList(){
V=parent.image.document.f1.list[parent.image.document.f1.list.selectedIndex].value;
if (V==80){top.location.href='index_burn.html'}
if (V==81 ¦ V==82 ¦ V==89){saveCookie1y("listCookie",V,X1y); top.location.reload()}}

Doubt that will help. What I'm really looking for is a description of the meanings of 7.0 error messages. The first one I'm getting is:

Error: uncaught exception: Permission denied to get property HTMLDocument.images

I do have something called document.images which I call from parent.create.document.images.

7.0 Help doesn't even have the word "permission" in it. I checked the index, glossary and search feature. Great.

Also in Preferences/Images I have "Accept all images" checked.

Thank you, Peter

P.S.

The problem went away when I saw the href line of code was working (above) and changed the reload() to an href like the other line. Not sure why this would make a difference as I'm hrefing the same page I'm reloading.?

[tedster]

An exception during the execution of a program is an event that interrupts the flow of instructions. If the program has a built in way to deal with that kind of exception -- a process of recovering from the error -- then that recovery is called "catching" the exception. So an "uncaught" exception is an error that occurs for which there is no built-in method of recovery.

Not a very helpful message from Netscape -- very generic.

I'm still checking out some of your other details, but I thought at least this much might help.

[ShawnR]

Hi Peter

You can find a reference for the DOM at [w3.org ]

Not sure if the following will help or further cloud the issue... Not even sure if I am correct, but for what it is worth:

I think what is happening is that HTMLDocument.images is a read-only attribute of HTMLDocument (see [w3.org ]). When you reload(), perhaps the way the browser is implemented it sees your call to parent.create.document.images as an attempt to write to a read-only object, whereas when you load the page afresh HTMLDocument.images does not exist before your call to create it.

Shawn