9002 2010-02-15 12:24:50 +0000 @sandbox should not allow content with text/html MIME type to force authors to change type to secure one. 2010-10-04 14:45:24 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#the-iframe-element P3 normal LC 1 contributor ian annevk ian mike public-html-admin public-html-wg-issue-tracking w3c public-html-bugzilla oldest_to_newest 32094 0 contributor 2010-02-15 12:24:50 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#the-iframe-element Comment: @sandbox should not allow content with text/html MIME type to force authors to change type to secure one. Posted from: 82.70.200.181 32095 1 annevk 2010-02-15 12:38:24 +0000 I assume this is meant to be a same-origin restriction? What happens if the restriction is not followed? 32100 2 w3c 2010-02-15 15:42:02 +0000 I don't think we should force use of the text/html-sandboxed media type because there are many use case that want to fail open in legacy browsers. For example, the ad and image search use cases I sent to the list. 32362 3 ian 2010-02-18 08:07:45 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: As Adam said, there are several use cases (like ads) for which failing open is perfectly acceptable. sandbox="" is only really supposed to be defense in depth, anyway, at least for the foreseeable future.