Safari javascript problem

using the onMouseover and newWindow scripts doesn't work

[corrigann]

For some reason my personal website isn't rendering properly in Safari. It renders perfectly in every other browser I have tried (FireFox, Camino, IE as well as their PC counterparts). Here is what I am trying to do:

the graphic links on the tops are coded with onMouseover events so that running the mouse over the graphic causes a rollover. As well, they are also links to other sections of the website, using open.window commands to open slightly smaller popup sections. I think that this combining of JS scripts is what's causing the page to render as plain black in Safari.

I tried running the site through a web based link checker, and it showed that my 'javascript.void(0) commands were possibly not supported by every browser. I have a version of the site without these commands, which renders the sam in Safari as just plain black.

The entire site is set within a table, that might be another factor in the site's incompatibility with Safari.

Any help that anyone could give would be greatly appreciated, I'm fairly new with JavaScript and could use the help of a professional.

Thanks.

Pierre M.

[edited by: rogerd at 6:11 pm (utc) on May 5, 2005]
[edit reason] No links/URLs, please... [/edit]

[BjarneDM]

1) start by fixing your validation errors
2) it's just so yesterday using javascript for changing images on links when hovering etc. a much better solution is using css for it

[whoisgregg]

Why is it all in an <object> tag?

[corrigann]

that was it, the <OBJECT> tag was causing the page to not load properly in Safari...I removed it and the page loads perfectly. Thanks so much for the help, all this time I assumed it was Safari's so-called javascript problems.

Couldn't say why the <OBJECT> tag was being used, a friend of mine coded the entire <TABLE> tag, I coded the javascript and designed the graphics....

Thanks again!

Pierre M.

[whoisgregg]

Glad to hear you could solve the problem. Since URL's aren't permitted here (and the link will surely disappear soon) the issue with this page was that the entire content was wrapped in an <object> tag.

While this may have validated, it apparently caused Safari to just ignore everything inside the tag. (I suspect every other browser just ignored the <object> tag.) Either way, don't wrap your page in an <object> tag. ;)