|
|
Posted by Chaddy2222 on 01/19/06 13:38
cwdjrxyz wrote:
> cwdjrxyz wrote:
>
> > I examined the php include in the auto page that processes the header
> > information. It is set up to use the true xhtml page only if it finds
> > the mime type application/xhtml+html mentioned by the browser as a
> > possible application when the server and browser first connect. If no
> > mention of this mime type is found, it takes the safe "else" path to
> > serve as html 4.01 strict, since anything else would require elaborate
> > browser and version detection that is far from safe. It is quite
> > posible a browser vendor could make an "xhtml ready" browser. That is,
> > it would handle xhtml served as html(which is no big deal), but it
> > could accept true xhtml served as such at some future time when the
> > browser vendor thinks the browser is ready and adds the correct mime
> > type for it in the header information the browser provides the server.
> > Such a "xhtml ready" browser might or might not support a page served
> > only as application/xhtml+xml or as application/xml. It might be
> > possible to hack around this if there really are any "xhtml ready"
> > browsers. However I can not afford to add extra computers to support
> > some of the browsers of interest, these browsers are not used very much
> > yet, and there would be many possible problems in detecting which
> > browser and version you had. Thus I am content to let any possible
> > "xhtml ready" browers receive xhtml 4.01 strict for now.
>
> I have added another page named
> http://www.cwdjr.info/extensions/autoForceXhtml.php .
> It is designed to automatically force the page to be served as
> application/xhtml+xml no matter what the browser says it will support
> or likes in the header exchange. Thus browsers that really will not
> support true xhtml 1.1 served properly will not display the page.
> However if there is a "xhtml ready" browser out there that really could
> support true xhtml, but does not because it does not mention it in the
> browser-server header exchange, this page may smoke it out. I give more
> discussion on the page if your browser allows you in. This new page
> gets in and displays for the recent Firefox, Netscape, Mozilla, Opera,
> and W3C Amaya browsers. It does not open the page for IE6 or Netscape
> 4.8, which of course it should not. Of course I do not know if there
> are really any "xhtml ready" browsers out there, and if there are I do
> not have them installed on my computer.
Well, your forced XHTML page seams to work fine in FireFox1.0.7, but
not in IE as you expected.
As a thaught, if you want to serve HTML in stead of XHTML, I would just
serve HTML4.01Strict too both browsers as it is a lot less work and may
save a lot of problems when rendering between, say IE7 and previous
versions of Ie. I also think that useing XHTML at the moment is a bit
pointless, as not even some PDA's support it.
--
Regards Chad. http://freewebdesign.cjb.cc
Navigation:
[Reply to this message]
|