- From: Doug Schepers <schepers@w3.org>
- Date: Wed, 13 Jan 2010 15:50:32 -0500
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- CC: Leonard Rosenthol <lrosenth@adobe.com>, Ian Hickson <ian@hixie.ch>, "public-html@w3.org" <public-html@w3.org>
Hi, folks- Tab Atkins Jr. wrote (on 1/13/10 10:23 AM): > On Wed, Jan 13, 2010 at 8:42 AM, Leonard > Rosenthol<lrosenth@adobe.com> wrote: >> I don't understand how you can assume that the destination of the >> doc URL is going to be text/HTML? Why couldn't the iFrame be >> pointing to an SVG image, for example, or a PDF? Those are also >> valid (and in the latter case of PDF, quite common) things one >> would put in an iFrame and wish to refer to... > > @doc doesn't take a url, it takes literal html code (with quotes > escaped). It is intended to help with the use of multiple<iframe>s > on a page, especially @sandbox'd ones, so that you don't incur > multiple network requests but still get the security benefits of > framing the content such as blog comments. The question still remains... would @doc allow SVG code, for example? Regards- -Doug Schepers W3C Team Contact, SVG and WebApps WGs
Received on Wednesday, 13 January 2010 20:50:37 UTC