Forum Moderators: mack

Message Too Old, No Replies

my site keeps crashing explorer

my site keeps crashing explorer

         

meanweaver

7:16 pm on May 14, 2004 (gmt 0)

10+ Year Member



I have just finished building my new site but i have a problem, when using I.E when i change pages i keep getting the error message that a fatal error has occured to i want to send a report, I thought it was something to do with the css navigation which that i got from this well known site.
<Snipped>

However i then went to test the feedback form and got the same message after hitting submit, the site was doing this locally when i was building it but i thought it would be a problem on my machine so ignored it, if i view it in netscape then all is fine, i have never come across this before so wondered if anyone else has, must confess that i have not tested it on any other machines as of yet but my I.E has never done this before.

Would be grateful of any help.
Regards Ian

[edited by: mack at 5:26 am (utc) on May 15, 2004]
[edit reason] Specifics removed. [/edit]

meanweaver

7:54 pm on May 14, 2004 (gmt 0)

10+ Year Member



If it helps narrow down my problem things seem to be ok if i take the link away from the stylesheet, but what can you put in a stylesheet to casuse this to happen, also found it will crash aol.

Please help!

pageoneresults

7:55 pm on May 14, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Are you using any z-index properties? I am able to crash IE by placing a z-index property on the body element.

bcolflesh

7:58 pm on May 14, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Start commenting out each line/item - check in browser - proceed to next line/item until you figure out which one is the problem.

meanweaver

10:59 pm on May 14, 2004 (gmt 0)

10+ Year Member



Have found my bug, When i started the site for some strange reason i put some background sound on it, however as the noise annoyed me when previewing the pages i left the code in but took out the path to the sound file and replaced it with # like you do when making a null link, and that was the problem, at least this code was right after the body tag so found it quickly.

Thanks for the reply's that got me thinking in the right way to find this bug.

Regards Ian