W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2012

[Bug 19752] New: Add sandboxed pointer lock flag to HTML Sandboxing

From: <bugzilla@jessica.w3.org>
Date: Mon, 29 Oct 2012 05:45:19 +0000
To: public-webapps@w3.org
Message-ID: <bug-19752-2927@http.www.w3.org/Bugs/Public/>

          Priority: P3
            Bug ID: 19752
                CC: ian@hixie.ch, mike@w3.org, public-webapps@w3.org,
                    robin@w3.org, scheib@chromium.org
          Assignee: silviapfeiffer1@gmail.com
           Summary: Add sandboxed pointer lock flag to HTML Sandboxing
        QA Contact: public-html-bugzilla@w3.org
          Severity: normal
    Classification: Unclassified
                OS: other
          Reporter: silviapfeiffer1@gmail.com
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: default
        Depends on: 18647
           Product: HTML.next

+++ This bug was initially created as a clone of Bug #18647 +++

Created to merge
which has been parked in feature/whatwg_iframe_pointer_lock branch.

Pointer Lock API [1] adds capability that should be restricted by a sandbox
flag unless an iframe is marked explicitly with sandbox="allow-pointer-lock"

Rough edit suggestion to HTML:

Add a section for The sandboxed pointer lock flag
+ "The sandboxed pointer lock flag
+  This flag prevents content from using the Pointer Lock API"
   with link to http://www.w3.org/TR/pointerlock/

Add a new flag parsing item:
After the text: "When the user agent is to parse a sandboxing directive ..."
+ "The sandboxed pointer lock flag, unless tokens contains the
allow-pointer-lock keyword"

[1] http://dvcs.w3.org/hg/pointerlock/raw-file/default/index.html

You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 29 October 2012 05:45:21 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:49 UTC