Well without any kind of link to your site we can't really help. I would assume it is some section of your style sheet that can't be used in IE or Safari, etc.
Try to check your site here first: http://validator.w3.org Fix all the errors if their are any, If the site is still broken, then you should post your CSS here.
Presuming your markup and CSS are both valid, one approach is to simply not support standards non-compliant browsers. Of course, a more conscientious approach would involve additional stylesheets for other browsers (commonly IE6). You have to understand how exactly IE6 misinterprets markup, however. If you provide your site details we should be able to figure out which bug is manifesting itself.
Or just code it well in the first place and you'll have no major bugs in any browser. IE6 may throw a few things at you, but most are relatively easy to solve. (min-height etc.) Using additional stylesheets or IE conditional comments is rarely needed. People on older operating systems, or even XP have no idea that an upgrade is available, and Firefox does not support Win95 (which some people still use), I think Opera does though, not sure. Do not drop support for IE6 - most IE users still use it, and that is a BIG market share. Code well, use minimalistic, well formed, semantic markup that is valid to either xHTML 1.0 Strict or HTML 4.01 Strict. F**k Transitional backwards... Never use Dreamweaver or Web Expression as it churns out crap code, and IMO cause more damage to the Internet than IE ever will. And Ozan, as for your site, did you try putting 'display:inline' onto the elements you have floated? That solves it pretty much everytime. For example: div.class{ float:left; margin-left:5em; } Code (markup): That will cause a float issue on IE6, but using: div.class{ float:left; margin-left:5em; display:inline; } Code (markup): won't. Cheers, BP
It may solve the immediate problem, but what happens when I want it to act like a block (which it is)? I agree that there are only a few known bugs that IE6 is going to throw up, but unless you're particularly conscious of them, they may be unexpected and difficult to identify. Many designers include additional css files with IE fixes. And they're of non-negligible length - the ie.css that ships with WordPress, for instance, has 30 or so selectors. Not something I was ready to do for the 2% of my readers who still use non-compliant browsers.
It still does. If not, check out inline-block... And with over 35% of users using IE6, goodbye decent traffic. Noone is going to upgrade browsers to view a site with no real content and disrupt their habits. And to be honest, IE6 is the least of your worries, it should also work without images, css and javascript (so on screenreaders like Lynx)
If you tell it to act inline, it acts inline. Sorry my question was supposed to be rhetorical. in IE6/7 it only works for elements that are inline by default (so not divs). While many sites experience 35% of users with IE6, I don't. Mine is closer to the 2% I mentioned previously. That includes users from high-bounce sources like stumbleupon. Is this addressed to me? I haven't tested my site on Lynx but it works fine on Fangs.
It appears you are trying to produce Interoperable web pages -- those that will display and function as intended in all user-agents (not just Graphical Browsers) -- congratulations and thank you for contributing to a more functional web! Check out this reference for more information. James
Making my sites browser friendly with at least the major 5 browsers so far takes the most time for me. I hate it.