W3C home > Mailing lists > Public > public-html@w3.org > January 2010

Re: <iframe doc="">

From: Joe D Williams <joedwil@earthlink.net>
Date: Thu, 14 Jan 2010 16:25:26 -0800
Message-ID: <D7F8885197044996BE9B941079F75331@joe1446a4150a8>
To: "Leif Halvard Silli" <xn--mlform-iua@xn--mlform-iua.no>
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?

If what you are asking is can you use <iframe> to import text/html 
into a browser-hosted document defined as application/xhtml+xml, then 
the imported stuff must obey xml and be in the default document 
namespace or parent namespace of the iframe? Somehow I don't think it 
must be the same parser working on both types.  So, whatever the 
initial doctype, then you must continue or your DOM may fail.

I mean for sure if you start with namespace xhtml+xml and strict xml 
parser, then start importing text/html what should the browser do?

Now it sounds like we want to drop documents or fragments into sandbox 
iframes for the purpose of isolating from the parent.
Why was I concerned about <iframe> putting html5 user code that 
actually did something in a new @doc attribute or allowing a non-html 
url in @src?

Thanks and Best Regards,
Joe




,
----- Original Message ----- 
From: "Leif Halvard Silli" <xn--mlform-iua@xn--mlform-iua.no>
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>
Sent: Thursday, January 14, 2010 2:31 PM
Subject: Re: <iframe doc="">


> 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 Friday, 15 January 2010 00:26:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:57 GMT