I believe there are some developer tools for IE but I tend to have 3 or 4 browsers open at the same time and just test in each as I go. I use Firebug for looking at code but when testing I work on the real code and load it into each browser.
| SitePoint Sponsor |


I believe there are some developer tools for IE but I tend to have 3 or 4 browsers open at the same time and just test in each as I go. I use Firebug for looking at code but when testing I work on the real code and load it into each browser.
www.pmob.co.uk CSS FAQ 3 col demo Read My CSS Articles
Ultimate CSS Reference
Check out SitePoint's latest JavaScript challenge

For me I just do basically the same as Paul, I look at hte code for FF and then if I spot something that could be an issue I go test it and that's generally good enough for me.
I tend to not even bother with IE develoepr toolbars (or chrome developer) because there isn't a real need for it. IE developer toolbar is quite horrible IMHO
Twitter-@Ryan_Reese09
http://www.ryanreese.us -Always looking for web design/development work





I use Firebug and IE developer toolbar almost exclusively for figuring out other people's pages... and mostly it's just the outline of Inspect Element. This has actually helped me figure out what IE has done with a disappearing element (I have found dropped and hidden floats in IE on others' pages using that). IE dev toolbar also tells you if IE considers the element to have Layout.
If it's my own code, it's faster to add background colours.
Thank you for the advise, all great. I know where I am going anytime I have an issue, I cant solve myself within an hour, SITEPOINT rules.
Thank you all again.
Bookmarks