- From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Date: Thu, 14 Jan 2010 23:31:11 +0100
- To: Joe D Williams <joedwil@earthlink.net>
- Cc: Maciej Stachowiak <mjs@apple.com>, Doug Schepers <schepers@w3.org>, "Tab Atkins Jr." <jackalmage@gmail.com>, Leonard Rosenthol <lrosenth@adobe.com>, Ian Hickson <ian@hixie.ch>, public-html@w3.org
Joe, you did not answer my question (or perhaps I was unclear): What if the <iframe> element resides in a XHTML5 document? Does @doc then still only permit text/html content? leif halvard silli Joe D Williams, Thu, 14 Jan 2010 13:24:16 -0800: >>>>> The question still remains... would @doc allow SVG code, for >>> >> example? > > Travelling down this road of trying to allow something else than > native html to be specified as content for <iframe> is being bit by > trantula. > When the iframe contains just html [...] > ----- Original Message ----- From: "Leif Halvard Silli" >> Maciej Stachowiak, Wed, 13 Jan 2010 12:52:20 -0800: >>>> The question still remains... would @doc allow SVG code, for example? >>> >>> Using SVG-in-HTML, yes (since it assumes a text/html MIME type). >>> Using the traditional XML serialization of SVG, no. >> >> And if I serve the HTML5 document as application/xhtml+xml, then what? >> Would @doc then still expect text/html - only?
Received on Thursday, 14 January 2010 22:48:00 UTC