[Bug 26934] New: [Shadow]: How should Element.requestPointerLock() work in shadow DOM? from bugzilla@jessica.w3.org on 2014-09-29 (public-webapps-bugzilla@w3.org from September 2014)

From: <bugzilla@jessica.w3.org>
Date: Mon, 29 Sep 2014 23:47:53 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-26934-2532@http.www.w3.org/Bugs/Public/>

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26934

            Bug ID: 26934
           Summary: [Shadow]: How should Element.requestPointerLock() work
                    in shadow DOM?
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Component Model
          Assignee: dglazkov@chromium.org
          Reporter: bugs@pettay.fi
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org
        Depends on: 26365

Currently requestPointerLock requires element to be in Document, but Chromium
does let one to lock pointer to a shadow dom element too.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 29 September 2014 23:47:55 UTC