POLL: Would you stop developing for IE7 to 'force' others to use Firefox/Safari etc?

[tomoisyourgod]

I think we must all agree that as web designers/developers we must always cater for all browsers.

At least then it seperates us from the ignorant designers/developers who cater only for one browser...

 

[janey]

got no choice.

*&#$ing hate testing in all the browsers I can get my hands on, but that's what Parallels and Boot Camp and my PC are for.

 

[jng]

A few months back I got a new job, and have been pretty succesful at moving over to 'Web 2.0' and using CSS to design my pages.

IE7 does fine rendering CSS 98% of the time. If sites are looking really messed up, you may want to practice your css a bit more. The only big issues I have with IE7 is the fact that they don't support the :before and :after pseudo class.

The key phrase in the OP is "pretty succesful [sic]."

I've been making websites for nearly 10 years now and when I first started designing in standards compliant XHTML and CSS, I also cursed out Microsoft (albeit mostly in private). The problem is that most designs don't fully understand CSS and its finer intricacies. I have to agree with Radiantm. Most of the time, IE7 works fine as long as you code properly. And I don't just mean validating.

And there are different ways of approaching CSS designs. I remember posting in a forum once, complaining about why IE6/7 didn't render my site properly. Somebody helped me out but in the process, restructured my CSS and XHTML entirely. And I learned from that that I was approaching it wrong.

For the most part, I don't have any major issues with IE7, indeed a vast improvement over IE6. And IE6 is a pain but not impossible. I just wish it supported PNGs better, esp. transparent PNGs.

Protesting by not having it work in IE? Agreed suicide. You're also then punishing your customers/visitors for your own inabilities (not just Microsoft's).