In article <>, says...
> > Ok, let's calm down here. What Spartanicus is trying to tell you is that
> > your are specifying your document as XHTML1.1, the problem is to be
> > valid XHTML1.1 the content type the server should send the document is
> > 'application/xhtml+xml'.
> > see:
> > http://www.w3.org/TR/xhtml-media-typ....xhtml#summary
> > Now the problem here is IE does not support 'application/xhtml+xml' only
> > 'text/html'. The fact that your see anything at all IE means the
> > document is being served as 'text/html' which means it is *not valid*
> > 'XHTML1.1' but 'XHTML 1.0 Transitional'. Now this is not exactly the
> > problem you were asking about, but is a fundamental problem with your
> > situation, and DOCTYPE does effect the render mode of the browser. If
> > you have an invalid DOCTYPE the render mode of the browser will be
> > unpredictable. Fix your basic error first then we can address the
> > subsequent problems.
> Thanks for clearing that up Jonathan
> This makes a lot more sense now =) I immidiatly checked my script,
> activated application/xhtml+xml and now I see IE doesn't parse it. I
> really thought I had it like that before, but it now seems I didn't.
> Sorry spartanicus for missing that, but I think I just needed a better
> I tried out both text/xml and application/xml. Firefox renders them
> fine, but IE rambles about dtd problems.
> So what does this mean. There is no way to use XHTML1.1 in a browser?
> This means
> (which also uses XHTML1.1 markup) is not valid (since it is served as
> If I'm correct I can change to XHTML 1.0 (HTML compatible). Just to be
> sure, can I still use strict?
> Thanks for pointing this out. I will give it a shot and hope it will
> also fix my original problem
But why use XHTML at all? What you are trying to achieve is easily
accomplished with HTML, and will render properly in IE.