<p>I'm not talking about tools that let one view a page in combinations of operating systems and browsers like crossbrowsertesting.com but in creating or figuring out the actual CSS.</p>

[{'answer_id': 26120, 'author': 'sparkes', 'author_id': 269, 'author_profile': 'https://Stackoverflow.com/users/269', 'pm_score': 0, 'selected': False, 'text': "<p>I write to the standards and both Firefox and IE7 follow a pretty good set in common.  </p>\n\n<p>IE6 is dead as far as I am concerned but if I get back into professional web dev I'll probably have to revise that ;)</p>\n"}, {'answer_id': 26126, 'author': 'Eli Courtwright', 'author_id': 1694, 'author_profile': 'https://Stackoverflow.com/users/1694', 'pm_score': 0, 'selected': False, 'text': "<p>I try to make a standards-compliant page and do all my testing in Firefox (since it has some excellent development extensions such as Web Developer and Firebug).  Then when I'm finished I test the site in IE, then make whatever small changes are necessary.  I find that I need to make very few changes, since I don't do anything extraordinarily complex with CSS.</p>\n\n<p>I used to have more problems with Javascript differences, but after I started using Javascript libraries (such as jQuery) I stopped having any serious problems with that.</p>\n"}, {'answer_id': 26127, 'author': 'Brian Warshaw', 'author_id': 1344, 'author_profile': 'https://Stackoverflow.com/users/1344', 'pm_score': 0, 'selected': False, 'text': '<p>Padding.</p>\n\n<p>IE6 can get a little hinky when using margin to place elements horizontally on a page. If you size your elements and space the content within using padding, you can make many layouts work great in IE6/7, FF, Safari, and Opera without any hacks. IE5.5 makes things a little stickier because of the broken box model, but I think we can pretty much count it out in most circumstances now.</p>\n'}, {'answer_id': 26131, 'author': 'Ross', 'author_id': 2025, 'author_profile': 'https://Stackoverflow.com/users/2025', 'pm_score': 0, 'selected': False, 'text': "<blockquote>\n  <p>I try to make a standards-compliant page and do all my testing in Firefox (since it has some excellent development extensions such as Web Developer and Firebug). Then when I'm finished I test the site in IE, then make whatever small changes are necessary. I find that I need to make very few changes, since I don't do anything extraordinarily complex with CSS.</p>\n</blockquote>\n\n<p>The same here, except I don't tend to need to use Firebug and such. I've only had problems with IE6 recently however - which are solved by simple CSS bypasses:</p>\n\n<pre><code>/* All browsers read: */\nhtml body {\n    margin: 10px;\n}\n\n/* FF, IE7, Op etc. read: */\nhtml &gt; body {\n    margin: 0;\n}\n</code></pre>\n"}, {'answer_id': 26134, 'author': 'John Sheehan', 'author_id': 1786, 'author_profile': 'https://Stackoverflow.com/users/1786', 'pm_score': 2, 'selected': False, 'text': '<p>Use a css reset to level the field across browsers. YUI and Eric Meyer have good ones.</p>\n'}, {'answer_id': 26140, 'author': 'Tom Carter', 'author_id': 2839, 'author_profile': 'https://Stackoverflow.com/users/2839', 'pm_score': 0, 'selected': False, 'text': '<p>I\'m with Eli.  Writing against firefox (with firebug installed) makes you have to write "more compatible" code to begin with and then its less of a job later down the line when you come to make it compatible with IE.</p>\n\n<p>Use the site <a href="http://www.quirksmode.org/" rel="nofollow noreferrer">QuirksMode</a> to help you find answers to compatbility information</p>\n'}, {'answer_id': 27096, 'author': 'Cade', 'author_id': 565, 'author_profile': 'https://Stackoverflow.com/users/565', 'pm_score': 3, 'selected': True, 'text': '<p>If you guys are still coding for IE6, you\'re making a mistake.  </p>\n\n<p>I use <strong>IE7.js</strong> to get IE6 to render pages like IE7.  IE7 is not perfect, but at least it has some semblance of standards.  Since I only have to code for IE7 and FF it makes me 33% more efficient in terms of testing against browsers, something I think makes good business sense.</p>\n\n<p>Link:  <a href="http://code.google.com/p/ie7-js/" rel="nofollow noreferrer">IE7.js</a></p>\n'}, {'answer_id': 27102, 'author': 'Al.', 'author_id': 2881, 'author_profile': 'https://Stackoverflow.com/users/2881', 'pm_score': 0, 'selected': False, 'text': "<p>If it's a brand new project I make it a point to test all html+css changes on all browsers I'm targeting as I make the changes. In the past I tended to focus on my favorite browser and then test with the others after I was done to find that one or more small quirks were present and it was very tedious to pin-point the actual cause. Now I have all browsers open and just go through refreshing each one after each html/css change to make sure the display meets my expectation. When something goes wrong, I know exactly what caused it.</p>\n\n<p>It might seem time-consuming to test on all browsers at once, but in the long-run it actually saves time as you catch the problems at once.</p>\n"}]
['https://Stackoverflow.com/questions/26113', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/2702/']