This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 9949 - there should be a way for developers to not allow their pages to be sandboxed, like if they absolutely need javascript.
Summary: there should be a way for developers to not allow their pages to be sandboxed...
Status: RESOLVED WORKSFORME
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-17 23:13 UTC by contributor
Modified: 2010-10-04 14:48 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2010-06-17 23:13:22 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#the-iframe-element

Comment:
there should be a way for developers to not allow their pages to be sandboxed,
like if they absolutely need javascript.

Posted from: 64.180.73.98
Comment 1 Adam Barth 2010-06-18 04:05:35 UTC 
What would happen when the "irresistible force" of required JavaScript hits the "immovable object" of a sandboxed iframe with JavaScript disabled?
Comment 2 Ian 'Hixie' Hickson 2010-08-28 00:06:10 UTC 
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: Accepted
Change Description: no spec change
Rationale: It's already possible. Just use hidden="" to hide your entire page except for a bit wrapped in <noscript> that announces to the user that the page refuses to play nice.