Microsoft: A lot of work ahead for CSS compliance

http://www.betanews.com/article/Microsoft_Lots_of_CSS_Work_Still_to_Do/1156280504
from WinCustomize Forums
Microsofts IE Program Manager says there is "a lot of work ahead of us" to get Internet Explorer up to CSS compliance. Although he did state that they have made over 200 behavior changes for CSS 2.1.

But no worries folks. Micrsoft has the answer to any problems you might have with your site and IE7. Just fix your site yourself to make it work with IE7.

"As we struggle to balance the needs of our user customers with the desires of web developers, we need your help. The only way for us to continue to improve our standards support is to get your help in changing your sites for IE7."

  

microsoft
4,747 views 5 replies
Reply #1 from JoeUser Forums Top
To run Vista we'll all have to have a machine with the same graphics card, sound card, hard drive, mouse, keyboard, monitor, etc. as every other Vista-running machine. And I'll stick to Mozilla.
Reply #2 from JoeUser Forums Top
GEEZ!  yea right!  I am so tired of sites (even this one) only working with IE.  I really wish the world would smack them and reject thier stupid hacks and get back to standards.
Star Control: Origins
Reply #3 from WinCustomize Forums Top
  
Reply #4 from WinCustomize Forums Top
I have actually been enjoying using IE7 in Vista, and I'm a Firefox fan usually. I only use Firefox in Vista when I come across a showstopper (which does happen quite often )
And to get my rage out now:
WHY THE **** DOES IE NOT LIKE THE MAX-WIDTH CSS PROPERTY?!
*calms down*
Reply #5 from WinCustomize Forums Top
Internet Explorer 6's, and to a much lesser extent IE7's, CSS display bugs are one of those things that just drive me nuts.

Website designers should be able to write standards compliant CSS, etc., and be confident that software claiming to be a "browser" will display it correctly. IE7 is much better than IE6, but I guess the attitude at the MSIE team that they ARE the standards hasn't changed much. Although, to be fair, I think the guy might have just been talking about changing one's DOCTYPEs or removing old workarounds smoothly.

If Microsoft wants to write an application with exclusive support of proprietary site code, nearly unpredictable treatment of existing standards, strangely overzealous security (IE7 reported my own personal site to me as a possible "phishing" site), and creepy cryptic record keeping aside being a prerequisite for key OS updates, they shouldn't call it a browser. They should call it "AOL-X" or "Web-TV for Computers" or something.

Not that Firefox is perfect, some javascript stuff makes some buttons here at WC jump around for instance, but at least FF draws what is in the HTML and CSS, not it's own artistic interpretation of the code. And with right extensions for FF I can have tabs of IE, and never have to lose much of FF's power.