RE: text/sandboxed-html

How would this work for content that references resources that require the use of a plugin to view?   

How would a UA know if the specific plugin can run sandboxed or not?  How would the UA communicate to the plugin that is should be running sandboxed? 

I would think that these problems would need to be addressed otherwise the usefulness of "sandboxed" is significantly reduced since it wouldn't actually mean anything in such contexts.

Leonard Rosenthol
Adobe Systems

-----Original Message-----
From: [] On Behalf Of Ian Hickson
Sent: Tuesday, January 12, 2010 8:52 PM
Subject: text/sandboxed-html

In response to implementor feedback regarding the sandbox="" feature of 
<iframe> in the WHATWG list [1], and based in part on a 2007 research 
paper from Microsoft [2], I have introduced a new MIME type for HTML 
(text/sandboxed-html) that is identical to text/html in every way except 
one critical aspect: resources served with this MIME type are forced into 
a unique security origin context.

This feature can also be used with <iframe sandbox=""> to force the 
desired behaviour in legacy UAs -- fallback to either no sandbox is 
possible as before (for the case where sandbox="" is being used for 
defence-in-depth), and fallback to load failure is now possible by serving 
the content with this type (for the case where legacy UAs are not intended 
to be supported and sandbox="" is being used for first-line security).

This is somewhat experimental, and so feedback (especially implementor 
feedback) regarding this proposal is encouraged.

Ian Hickson               U+1047E                )\._.,--....,'``.    fL       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

Received on Wednesday, 13 January 2010 14:38:47 UTC