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

Re: Trying to use <iframe srcdoc= >

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Mon, 25 Jan 2010 17:44:01 -0600
Message-ID: <dd0fbad1001251544u686021ffo83c4889857ca3842@mail.gmail.com>
To: Gavin Carothers <gavin@carothers.name>
Cc: HTMLwg <public-html@w3.org>
On Mon, Jan 25, 2010 at 5:35 PM, Gavin Carothers <gavin@carothers.name> wrote:
> On Mon, Jan 25, 2010 at 3:24 PM, Smylers <Smylers@stripey.com> wrote:
>> Gavin Carothers writes:
>>
>>> No browser today supports srcdoc, and when it fails no content is
>>> shown on the page. ... Am I missing something?
>>
>> That HTML5 is far from implemented in widely deployed browsers.
>>
>> You're correct that this feature can't be used right now.  There are all
>> sorts of HTML, CSS, and JavaScript features which couldn't be used at
>> the time they were specced but which are now an everyday part of
>> webpages; we just had to wait patiently a few years till they were
>> usable.
>>
>> <iframe sandbox srcdoc="..."> is like that, in that it's only intended
>> to be used by authors once browser support it.
>
> My worry is that with such a painful fall back experience it won't be
> usable for even longer. Yes lots of HTML, CSS, and JavaScript features
> couldn't be used when spec'd, but they started being used when only a
> small percentage supported it. With this, I can't really see
> supporting it as a publisher/author until a HUGE percentage of
> browsers support it. :\

I wouldn't recommend even trying to use it until virtually all
browsers support @sandbox.  There is a fallback story, but it's just
"fail at showing anything" for security reasons.

~TJ
Received on Monday, 25 January 2010 23:44:52 GMT

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