Hi guys! I have just started to design in CSS - Table less approach My questions are: 1) how i can code my css for different browsers? 2) what browsers and resolutions i need to test my css design? so it would be same in IE or in any other browser?
Write your markup using current standards and generally it will work in all browsers (sometimes even IE). Test your browser in the most standards compliant browser available (that means NEVER IE). Once you know your markup is working, then check to see if/when IE screws things up.
theres no need to code for diff browsers its up 2 the browsers to follow standards if they dont its there problems as long as you're following standards its ok. as for resolutions try 2 avoid horizonal scrolling
Well... The guys are right. Code within the standards and leave IE worries aside until you're done. If your css then validates but your site looks bad in IE, the best fix would be to create a separe css file for it and correct the errors rendered in IE in that file. To check your site in all versions of IE you can use IE Tester (google it). Better than just some still images like browsershots give you.
What? I'm sorry but that's the dumbest thing I've read in awhile. It's the complete opposite. The standards set out by W3 are a guideline on how to make a website, not absolute laws that must be followed. You want your website to work in as many browsers as possible, if not ALL browsers. Using hacks to make your site in Internet Explorer is okay. It's perfectly fine. Yes, your site will not validate, but ask any professional web developer, and they will tell you the exact same thing - it doesn't make a difference because W3 is only a guideline to help you, the coder. Your site should work in all these browsers (in order of importance): 1. Internet Explorer 7 2. Internet Explorer 8 3. FireFox 4. Internet Explorer 6 5. Safari 6. Opera 7. Other If you can't get it pixel perfect, simply make a css comment that specifies to only Internet Explorer. It's very easy to do.
So if you don't want to follow the W3C, who do YOU follow? Microsoft and Mozilla and Opera and Apple all wrote those standards and signed off on them and advocate you using them so who do YOU follow? I'm a professional coder and I say that's a line of BS. If you can't make your page standards compliant then you are incompetent. More BS. Test in a modern, standards compliant browser first, which is NEVER any version of IE. Then and only then check to see if and when IE screws it up. You can apply 'conditional comments' to fix IE. Even Microsoft warns to beware of "hacks" in the new browser and not to use them!
For testing your page in different IE versions, use IETester (http: //www.my-debugbar.com/wiki/IETester/HomePage). IETester contains IE8,IE7,IE6 and IE5.5, so It will help you much. Like it or not, we cannot ignore the fact that IE is a most used web browser in the world. So make sure that IE users can view your website displayed properly like in other browsers.
Well then you need to correct yourself before you get worse. I've never seen posts like yours among devs who know what they're doing.
That's not actually factual. The standards are written for those who implement the user agents; not for those who author for those UAs. Browsers are programmed to work as described in the recommendations. Some are better/worse than others. It is incumbent on web authors to write according to these standards. There have been forum comments implying that there are no standards, only recommendations; as if a recommendation had little weight. These people are ignorant of the Way Things Work®. The W3C calls their standards "recommendations". They are still the standards, and if you ignore them when authoring a page, you risk indeterminant results. The IETF calls their standards "Request for Comments" (RFCs). They are not any less standards for being RFCs. Try sending an email with your home-coded mail agent that doesn't comply with RFC 2822. Good luck with getting through. IEC/ISO calls their standards "standards". Whatever is the world coming to? Even if called standards, they are not any more binding than W3C's recommendations, or IETF's RFCs. cheers, gary
You code to standards not to browsers, if a browser messes it up it is simply the browsers problem, not the coders (presuming it is not a coding error). Browsers that mess things up would not be well known anyway, IE only is because it's MS and all, why should I go out of my way to add hacks for their inabilities? Imo it is on the browsers to get things to display the same way, and the only way to do that is to set standards.. I'd rather have good code which worked in no browser than thousands of lines bad code which was browser compatabile.