- From: <bugzilla@jessica.w3.org>
- Date: Thu, 25 Oct 2012 18:10:19 +0000
- To: public-webapps-bugzilla@w3.org
- Message-ID: <bug-18647-2532-c2i8WwL6oZ@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18647
Ian 'Hixie' Hickson <ian@hixie.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ian@hixie.ch,
| |public-webapps@w3.org
Component|HTML |Pointer Lock
Assignee|ian@hixie.ch |scheib@chromium.org
Product|WHATWG |WebAppsWG
QA Contact|contributor@whatwg.org |public-webapps-bugzilla@w3.
| |org
--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch> ---
Ok, I have added "allow-pointer-lock" to the HTML spec.
In the Pointer Lock spec, add the following clause somewhere:
If [the Document object]'s _active sandboxing flag set_ has the _sandboxed
pointer lock browsing context flag_, then [the user agent must not lock the
pointer].
...where
"the Document object" should be expanded to a reference to the Document
object
for which pointer lock is being enabled, whatever that is.
"active sandboxing flag set" and "sandboxed pointer lock browsing context
flag"
are terms now defined in the HTML spec.
"the user agent must not lock the pointer" is whatever conformance
requirement
you need to add to your spec to make it not lock the pointer.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 25 October 2012 18:10:21 UTC