Help with IE 6

[TLuck234]

Not sure how many people still have IE 6 on there computer, but I need some help debugging some code. If you could visit

http://rockets34.com/history.php

And let me know how it works on your computer that would be great. I'm currently using jQuery to do tabs on this page. For some odd reason, Safari and Chrome will not run this jQuery tab. So I have javascript deciding on if the browser is Internet Explorer/Firefox or Safari/Chrome, and then the page is rendered differently depending on that. Everything was working smooth for awhile, but now when I try to open the page in IE6, it crashes. Don't know if it is me or not, would love for some feedback. I'm about to run the Windows file scanner again and see if that fixes it. The code and scripts work great on everything but IE 6. Always been a horrible browser.

Thanks

[hyperdude]

It works fine for me, in Firefox 3.6.

Simple solution to your IE6 problem: Don't use it. Work on making the site compatible with IE6, but don't get too hung up on it. After all, the Website judges are supposed to check that the site works in all major browsers - if it works in IE6, that should be enough.

[TLuck234]

Originally Posted by hyperdude

It works fine for me, in Firefox 3.6.

Simple solution to your IE6 problem: Don't use it. Work on making the site compatible with IE6, but don't get too hung up on it. After all, the Website judges are supposed to check that the site works in all major browsers - if it works in IE6, that should be enough.

Very true. Thanks for the quick reply.

[GGCO]

Google has stopped supporting IE6 - don't worry about it.

[Dan Zollman]

I get a syntax error from line 121 when I visit the page in IETester.

However, the page looks empty (I see the header and main menu, but nothing in the content area), no matter which browser I use.

Regarding the question of supporting IE6 in the first place...

There's only one way to find out whether or not you should support IE6, and the answer may be "yes" for one team, "partially" for another team, and "no" for another team: What do your visitors use?

If you don't have an analytics system installed, sign up for Google Analytics (it's free) and install it on your site (it's quick and easy). Let it collect data for two or three or four weeks. It'll tell you how many of your visitors are using each browser, as well as each version of each browser.

Based on that number, you can decide how important it is to you to support those visitors. You could a) not support them at all, b) support them partially, and make the site viewable and usable even without providing all the features (hopefully in a way that the visitor doesn't even notice things are missing), or c) support them completely.

Feasibility of support is another factor...but it's important to know the implications of each option before you choose one. (My vote's for B, though.)

[TLuck234]

Originally Posted by Dan Zollman

I get a syntax error from line 121 when I visit the page in IETester.

However, the page looks empty (I see the header and main menu, but nothing in the content area), no matter which browser I use.

Regarding the question of supporting IE6 in the first place...

There's only one way to find out whether or not you should support IE6, and the answer may be "yes" for one team, "partially" for another team, and "no" for another team: What do your visitors use?

If you don't have an analytics system installed, sign up for Google Analytics (it's free) and install it on your site (it's quick and easy). Let it collect data for two or three or four weeks. It'll tell you how many of your visitors are using each browser, as well as each version of each browser.

Based on that number, you can decide how important it is to you to support those visitors. You could a) not support them at all, b) support them partially, and make the site viewable and usable even without providing all the features (hopefully in a way that the visitor doesn't even notice things are missing), or c) support them completely.

Feasibility of support is another factor...but it's important to know the implications of each option before you choose one. (My vote's for B, though.)

That's a good idea. I'll need to do that. But, you said you don't see any content at all no matter what browser you are using?

UPDATE: Just fixed that. I was validating that page and put an error in there. Should work fine now.

[Dan Zollman]

Now it's crashing for me, too.

If you sacrificed the fading, you might be able to get away without jQuery and write JS for that feature by hand.

I'm sure there's also a way to fix the bug and still use jQuery, since jQuery is supposed to be compatible with IE6...but I don't know enough about jQuery to suggest a way of approaching that.

[Tom Line]

Originally Posted by GGCO

Google has stopped supporting IE6 - don't worry about it.

That is extremely flawed logic.

Many major corporations are still using IE6 because of their update / security IT cycles. By ruling out any major browser, you may be artificially limiting yourself. Tens of thousands of employees at my company would be totally unable to see the page if you simply throw IE6 out the window, and I gaurantee others are the same.

Also, Google hasn't technically stopped supporting IE6. All their current features will continue to function in IE6. They simply won't be checking new feature compatibility against the browser.

So an IE6 user will still be able to view youtube videos, check his Gmail, and use googledocs. That's a far cry from just ignoring total compatibility.

I would be very concerned if I were in the website competition - because one of the judges just might be using an IE6 machine at one of those giant corporations.

[WebTeam]

With in the code of your page you have -
<!--[if lte IE 6]>
<script type="text/javascript" src="supersleight.js"></script>
<link href="ie.css" rel="stylesheet" type="text/css" />
<![endif]-->
<!--[if IE 7]>
<link href="ie7.css" rel="stylesheet" type="text/css" />
<![endif]-->


Eliminate the <!--[if lte IE 6]> statement at the beginning of the Script code and the <![endif]--> at the end of the IE6 scripts Those scripts are non functional with those two lines surrounding them.

If this doesn't work there are other ways to have the page forward to a totally new url page for IE 6 only browsers

Hope this helps
http://team573.com

[Dan Zollman]

Originally Posted by WebTeam

Eliminate the <!--[if lte IE 6]> statement at the beginning of the Script code and the <![endif]--> at the end of the IE6 scripts Those scripts are non functional with those two lines surrounding them.

Normally that would be correct; however, in this case, these are conditional comments which are processed be IE only.

http://www.quirksmode.org/css/condcom.html
http://msdn.microsoft.com/en-us/libr...8VS.85%29.aspx

Wouldn't hurt to remove them temporarily for debugging purposes, though.