Layout In old IE's

[cfgcjm]

I've just developed a new website and It is pretty close to flawless in all OS's; FF, Opera, Safari, and IE 7. I'm assuming since such a large portion of web users still use IE6 I should develop pages specifically for them? Additionally do I need to go any further back in IE browsers as far as compatibility or is 6 far enough?

[apeace]

First of all, don't worry about any IE's except 7 and 6. If it works great in IE7, that's great.

So, does your web site not work in IE6? If that's the case, I guess you COULD just develop alternate pages for them. However...that's not the best choice. You should just try and code your pages so they work in IE6. If you need help with that, post a link to your site, and the community and I will all help you out.

Peace!

[felgall]

Unless you get millions of visitors a day the small fraction of 1% of visitors still using versions of IE < 6 should be few enough people to not worry about them.

[cfgcjm]

well i really don't want to have to develop a different style sheet for my site's IE 6 users but look at what IE 6 does to the page...

The issues are layouts and IE 6 doesn't support my png transparency

With FF & IE 7
http://stjohns.digiconmediagroup.com/2.jpg

With IE 6
http://stjohns.digiconmediagroup.com/1.jpg

[apeace]

Sorry, but I don't have the time to go through a whole layout, though I wish I could :( If you feel like paying hourly compensation, I can either fix it or re-code it, and even post the results here in the forum!

A tip: start coding the design again. Along the way, check out the results in both FF and IE6.

The key to creating a compatible site is writing strict XHTML and trying to keep in line with accessibility standards. Surprisingly, doing just these two things often results in a site that is compatible with all browsers.

I hope this helps, for what it is worth. :/

[Centauri]

You can't blame IE6 totally here - there is one error in the styling which you attempted to compensate for that breaks IE6....

You have set the width of #utilityholder at 24px, and in FF the 183px wide contents will spill out the side (but not in IE6). When this was right floated, it was too far right (due to the narrow width) so you compensated with a negative left offset - this is what makes the sidebar overlap in IE6. The width of #utilityholder should be set to 183px.

Next, the left side at 24px plus the content at 721px plus the right side at 183px equals a total width of 928px, which is what the width of #wrapper should be set to.

#contactbox width should also match #utilityholder at 183px, and a clear:right on this will position it correctly without that large top offset.

All you have to do for IE6 then is account for its 3px jog which will probably force the center content down, and apply the png fix - not major dramas.

[KDLA]

Sorry, but I don't have the time to go through a whole layout, though I wish I could :( If you feel like paying hourly compensation, I can either fix it or re-code it, and even post the results here in the forum!
Please note that advertising services is not allowed in this forum.
KDLA

[KDLA]

Centauri's right -- take his/her good advice.

Almost all problems arising in IE6 (if your coding is standard) are attributable to width and/or floats. Some nudges here and there usually fix them. ;)

[apeace]

Please note that advertising services is not allowed in this forum.
KDLA

My bad :/

Shall not do again! Thank you KDLA.

[WebJoel]

....check out the results in both FF and IE6... You can check the visual conformity upon several, or a few dozen(!) different browser/platform combination at browsershots.org

[KDLA]

You can check the visual conformity upon several, or a few dozen(!) different browser/platform combination at browsershots.org

Agreed :D This is a great tool, too:
http://tredosoft.com/Multiple_IE
This allows you to run several versions of IE on your PC. So, you could upgrade your regular browser to IE7, and then use this to render pages in IE6 and below.
It is GREAT for testing in that it is an actual HTML rendering, not a static .jpg.