|
|
Posted by cwdjrxyz on 01/19/06 18:58
Toby Inkster wrote:
> cwdjrxyz wrote:
>
> > As the IE6 does not support true xhtml served properly and apparently
> > neither will the upcoming IE7, you have nothing to fear for your
> > Safari. You can start to worry when IE supports true xhtml and xhtml
> > takes off on many sites, if it ever does.
>
> Safari has good support XHTML support, and has done since it was in beta
> testing.
I think that Dorayme, in his latest post, may have provided the answer
for Safari. It can be forced to go the true xhtml route if one does
that in the header/server exchange and allows no other options. This is
nearly, but not absolute, evidence that Safari does not provide the
mime type application/xhtml+xml as an option, since it takes the 4.01
route using the auto page and many other browsers will take the true
xhtml route if offered at all by the browser by the header/server
exchange. If I had a Safari browser, I could write many test php header
programs to run down all of the details, but I do not. Whatever the
reason that Safari responds the way it does, at least no harm will be
done if it gets a page as html 4.01 strict rather than true xhtml 1.1.
If, on the other hand, a browser that can not handle xhtml 1.1 got a
page written in it, this would be a problem. In theory, detection of
the Safari browser and version number could be used to force true xhtml
for Safari. However, in these days when browsers spoof one another,
detection of browser name and version has fallen into disfavor - many
have locked out some browsers by using it.
Navigation:
[Reply to this message]
|