W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > January 2010

[Bug 8725] New: text/sandboxed-html vs <iframe sandbox> and backcompat

From: <bugzilla@wiggum.w3.org>
Date: Tue, 12 Jan 2010 12:14:21 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-8725-2486@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8725

           Summary: text/sandboxed-html vs <iframe sandbox> and backcompat
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec bugs
        AssignedTo: dave.null@w3.org
        ReportedBy: simonp@opera.com
         QAContact: public-html-bugzilla@w3.org
                CC: ian@hixie.ch, mike@w3.org, public-html@w3.org


http://html5.org/tools/web-apps-tracker?from=4580&to=4581

text/sandboxed-html and <iframe sandbox> don't have the same backcompat story.
Is this intentional? It seems to me that we either want a parameter for
text/html or a new element.

Also: do we care about sandboxed XHTML or SVG?


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 12 January 2010 12:14:23 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:09 UTC