Hi Eric,

Thanks for your message.   We are in the process of rolling in XHTML support.  Some of the utilities already convert the tag case before testing tagName.

While converting tag case will get us closer to XHTML compliance, it will not make us fully compliant.  But its a good start.

We will continue to address this issue, the initial goal being to not break for this environment.

One thing that would help us greatly is for people to log specific issues encountered in this enviroment:
http://sourceforge.net/tracker/?group_id=165715&atid=836476

Thanks,

Matt

Eric van der Vlist wrote:

Le lundi 11 septembre 2006 à 16:26 -0700, Charles a écrit :

Seeing strange errors pop up when using the YUI with documents

served under application/xhtml+xml, I realize that YUI doesn't support
this even though this is the standard way to serve XHTML documents...
I think you're confused. No versions of IE (even IE7) support this,
for example.
http://www.w3.org/People/mimasa/test/xhtml/media-types/results

Yes, I know but I am a Linux/Firefox user and that's giving an incentive
to IE users to migrate to Firefox, Opera, Safari or Konqueror :) ...
More seriously, it's quite trivial to do content negotiation and serve
the same pages with a application/xhtml+xml media type for browsers that
declare they support it in the Accept: HTTP header and text/html for the
others.
It's an easy way to be fully compliant with the standards and still
display correctly in browsers that don't support them.
Eric