Forum Moderators: open

Message Too Old, No Replies

ie6 anchor problem, need some direction

ie6 html javascript anchor problem timeout

         

corgan1003

3:09 pm on Aug 6, 2007 (gmt 0)

10+ Year Member



I have a very interesting problem that I am not sure about. I use a hyperlink by calling a javascript function:

 onclick="javascript:document.formname.GOTOPAGE.value = 'Page2#Addinfo';

I am on "Page1", and this is supposed to take me to "Page2" and anchor at "Addinfo". This works fine in Mozilla Firefox and IE7, however, in IE6, there is a problem. "Page2" does not really load at all. In fact, the head nav bar of the page loads twice and then nothing beneath. I have tried quirks mode and this does not fix it. I suspect it is a timeout issue but in that case, I am not sure why the problem would be specific to ie6. Any direction would be much appreciated.

Thank you! (I just joined today so this is my first post but I will be sure to actively participate in this forum because it looks great)

tedster

6:45 pm on Aug 6, 2007 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Welcome to the forums, corgan1003.

Have your validated the html for page2? That's where I'd start, anyway.

W3C Validator - HTML [validator.w3.org]
W3C Validator - CSS [jigsaw.w3.org]

corgan1003

7:10 pm on Aug 6, 2007 (gmt 0)

10+ Year Member



I tried to validate but I have ~70 errors. I really think that validation is not the problem here. If you think so, can you explain a little bit? I would suspect validation is an issue if the page was anchoring at the wrong point, but the page is not even loading properly. Regardless, thank you for responding....this is my first forum so it feels good to be acknowledged.

Marshall

7:33 pm on Aug 6, 2007 (gmt 0)

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



Is there a reason you are using javascript rather than a normal link?

Marshall

tedster

8:01 pm on Aug 6, 2007 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I really think that validation is not the problem here. If you think so, can you explain a little bit?

Whenever you are working with a display problem that appears in one browser and not another, coding errors can make it literally impossible to find a fix. Every browser has it's own dedicated form of error-correction, and whatever that is in each case is not going to be visible to you.

So I find it best to make sure the page is on a "completely level base" before I try to work with finding a cross-browser fix. This would also include validating the CSS [jigsaw.w3.org].

corgan1003

11:04 pm on Aug 6, 2007 (gmt 0)

10+ Year Member



Marshall:

I am using javascript because the link is for a form that I validate with a javascript function. I did not provide the full code because I did not think it was necessary to understand the question.

I may try to CSS validate if it does not take to long. Thanks for the advice!