[Bug 12792] New: Publish the polyglot 'Sample Page' as 'application/xhtml+xml'

http://www.w3.org/Bugs/Public/show_bug.cgi?id=12792

           Summary: Publish the polyglot 'Sample Page' as
                    'application/xhtml+xml'
           Product: HTML WG
           Version: unspecified
          Platform: Macintosh
               URL: http://www.w3.org/TR/html-polyglot/#example-document
        OS/Version: Mac System 9.x
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML/XHTML Compatibility Authoring Guide (ed: Eliot
                    Graff)
        AssignedTo: eliotgra@microsoft.com
        ReportedBy: xn--mlform-iua@xn--mlform-iua.no
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org, eliotgra@microsoft.com


PROBLEM: The current version of Safari does not render the SVG of the
SamplePage. The sample page:

http://dev.w3.org/html5/html-xhtml-author-guide/SamplePage.html

The reason for this is that the page is served as 'text/html', and that legacy
user agents do not support SVG in 'text/html' mode.

Therefore, the page should be served as 'application/xhtml+xml' instead,
however preferrably _still_ with the file extension .html.

BENEFITS:

1) Demonstrates the features of polyglot markup.

2) All HTTP-conforming, legacy user agents (including legacy Webkit based ones)
will perceive it as XML, and will thus - if they support XML - render the SVG.

3) Some HTTP-non-conforming, legacy user agents will - due to the .html
extension -  "sniff" the document as "text/html". This will make then render
everything *but* the SVG. (Alternatively, if the page is served with a .xhtml
extension, those UAs will not render it all.) [Of course, a sub-issue here is
how to provie some kind of fallback to those user agents.]

HOWTO:  Simply change the file name from 'SamplePage.html' to
'SamplePage.html.xhtml'. That's should be it (provided Apache is set up as it
usually is). Do not change the link to the page. Then IE9 will treat it as
XHTMl, while IE6-IE8 will treat it as HTML.

Example page that does the same thing:
http://www.malform.no/messages/issue-30.html
http://www.malform.no/messages/issue-30.html.utf8.xhtml

Additionally/Optionally, you cold also add "proper" content negotation too.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 25 May 2011 23:06:29 UTC