DrDoc - 2:00 am on Oct 19, 2004 (gmt 0)

jittery position:fixed?

Don't think so ;) [dean.edwards.name]

JS turned off

Yes, that's a problem. And, that's where the biggest decision maker may lie. You know your audience. Personally, I don't do much with IE7 (or anything else that requires JS) on sites I work with, simply because my audience may not have JavaScript enabled. Then again, most people using IE do not know how to disable JS in their browser.

To me, it's all about weighing the benefits, the pros and cons. Most of the time I'm not relying on CSS advanced enough to need more than a few simple style rules to "fix" IE. True, I could use IE7 to correct the "problems", but is it worth it? Not if I can do it in a much simpler and easier way myself. IE7 is great if you don't want to worry about various bug fixes on your own...

If I were just starting out with CSS I'd be all over IE7. But now, with the hard work that has been put in so far to learn CSS from the bottom up? Nah!

IE7 is great. I can really see its value and benefits. But whether or not to use it should be determined for each individual project, and by each and every developer.

There's no "one answer fits all" solution to the IE-lacking-standards-support problem...