On Mon, 23 Apr 2007, Jonas Sicking wrote:
There's a big difference to that and to what I'm proposing. With what's
in bug 80713 you're still limited to a box that basically doesn't take
part of the outer page at all. For example in the table example in my
original post the headers of the
PROTECTED], HTMLWG [EMAIL PROTECTED],
public-webapi@w3.org
[image removed]
Subject
[image removed]
Re: The iframe element and sandboxing ideas
[image removed]
[image removed]
Ian Hickson wrote:
Summary:
* I've added a sandbox= attribute to iframe, which by default
disables
On Wed, May 21, 2008 at 3:30 PM, Ian Hickson [EMAIL PROTECTED] wrote:
* I've added a seamless= boolean attribute to iframe, which, if
the content's active document's URI has the same origin as the
container, causes the iframe to size vertically to the bounding box
of the contents, and
Ian Hickson wrote:
Summary:
* I've added a sandbox= attribute to iframe, which by default
disables a number of features and takes a space-separated list of
features to re-enable:
[snip list]
Unless I'm missing something, this attribute is useless in practice
because legacy browsers
Re: The iframe element and
sandboxing ideas
PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Martin Atkins
Sent: Thursday, May 22, 2008 2:21 PM
To: Ian Hickson
Cc: public-webapi@w3.org; whatwg; HTMLWG
Subject: Re: [whatwg] The iframe element and sandboxing ideas
Ian Hickson wrote:
Summary:
* I've added a sandbox= attribute to iframe
Ian Hickson wrote:
- by default, content in sandboxed browsing contexts, and any
browsing contexts nested in them
How do those nested browsing contexts come about, given that later you say:
- content in those browsing contexts cannot create new browsing
contexts or
,
Chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Boris Zbarsky
Sent: Thursday, May 22, 2008 6:27 PM
To: Ian Hickson
Cc: public-webapi@w3.org; whatwg; HTMLWG
Subject: Re: [whatwg] The iframe element and sandboxing ideas
Ian Hickson wrote
Kristof Zelechovski wrote:
1. Nested browsing contexts in a sandboxed frame cannot be created
dynamically but they can be defined by the inner markup.
There was no mention of dynamically in Ian's proposal. My assumption
was that cannot create browsing contexts meant just that. If it
Ian Hickson wrote:
Summary:
* I've added a sandbox= attribute to iframe, which by default
disables a number of features and takes a space-separated list of
features to re-enable:
...
Makes sense, Ian.
Additionally to this, what about adding meta tag that disables or
limits
10 matches
Mail list logo
