Actually it easier than that, you can setup your own style sheet for the browser and there is a way to force individual styles to comply 100% with W3C standards. I can't remember how it's done but I am sure it in on their site.
You learn something new everyday. I never realized this was possible... though of course, I haven't spent "too much" time reviewing IE7 changes or the latest FF changes. That's pretty cool, and I need to look into this. I'd love to enforce some of my own, on plenty of sites.
You have to forgive my insistance on W3C compliance. I have been coding since at least the late 90's may be longer and things like marquee have come and gone in the past. And all it takes is one new browser version and your ingenius design is now completely usless. You should see my code from some of the first sites I did (I keep all my code) most of it is completely unrecognisable.
Heehee, I do know what you mean. I've been coding DHTML/ASP since 99 and much of my stuff is... well, I just look back and go "What was I thinking?!" all the time. Heck, some of my webcode from a year ago, I say the same thing.
I must admit though, that I have a different mentality than most when in regards to standards. I'm all for them , and find them entirely important... but I think conditions allow for rules to be broken if the risk is right. MS deisgns a LOT of DHTML coding for their browser which isn't usable anywhere else... but it makes life SOooooo much easier in many areas, and sometimes adds some stellar functionality.
Obviously, Marquee is an archaic example of that... Still, it's become a standard in it's own right... just like 'Noob' is a gaming lingo standard because it's been widely adopted.
I predominantly code for IE 6.5+ compliance as I write B-to-B applications where I can enforce the Browser type. However, I understand W3C compliance as all my apps aren't totally B-to-B apps. Still, it gives me a bent toward situational rules. If the risk isn't as bad as the gain... go for it. Just be aware of what the risk IS.