Comments on: Microsoft backs off XHTML support in Whidbey

By: pavel

pavel — Wed, 22 Feb 2006 02:39:12 +0000

they should have released IE 7 with asp.net 2.0 (make sure that IE 7 completely complies with standards)

bad project management…

IMHO, They release IE 7. Good project manager:)

By: pwpaust

pwpaust — Tue, 20 Dec 2005 00:13:27 +0000

they should have released IE 7 with asp.net 2.0 (make sure that IE 7 completely complies with standards)

bad project management…

By: Stinkbug.net » Blog Archive » Microsoft backs off XHTML support in Whidbey

Mon, 24 Oct 2005 16:27:47 +0000

[…] Microsoft backs off XHTML support in Whidbey While on the surface it may seem that Microsoft is taking a step back in standards-compliance, in fact it is demonstrating a healthy respect for Web standards by acknowledging that it must bring its browser up to scratch before adopting XHTML 1.1 in its Web application platform.read more | digg story […]

By: Milan Negovan

Milan Negovan — Tue, 06 Sep 2005 21:24:10 +0000

Personally, I welcome this change. I’ve discussed with Microsoft folks potential problems with XHTML 1.1 before. I’m glad they pulled the plug on 1.1 for now.

By: charmedlover

charmedlover — Thu, 01 Sep 2005 11:50:56 +0000

The whole XHTML issue has really pissed me off in my situations. In my latest project development I have to have a script to apply the correct MIME type to only browsers that can handle it. While I don’t mind this, I don’t like the idea of feeding tag soup to a browser - it just isn’t XHTML.

This was one of the major factors that would cause me to remotely like IE7.

By: Pig Pen » Microsoft Backs Off XHTML Support In Whidbey - its an adventure

Pig Pen » Microsoft Backs Off XHTML Support In Whidbey - its an adventure — Thu, 01 Sep 2005 10:42:19 +0000

[…] Microsoft Backs Off XHTML Support In Whidbey Top […]

By: mmj

mmj — Thu, 01 Sep 2005 04:59:50 +0000

I realise this seems pedantic, but the XHTML problem with Internet Explorer is not that it doesn’t support the application/xhtml+xml MIME type, but that it doesn’t support XHTML at all. Claims that IE doesn’t support the application/xhtml+xml MIME type makes it sound like it could be solved with one line of source code, but it’s not as simple as that. When IE encounters XHTML content it will parse it with an HTML parser (actually, a tag soup parser). It has real implications. For instance, when receiving XHTML, IE can’t cope with CDATA sections, XML stylesheets, or XML processing instructions - all aspects of XHTML that have no equivalent in HTML.