The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/d148a25d4b552d08fe0971faf9464c17cedc7e8f

commit d148a25d4b552d08fe0971faf9464c17cedc7e8f
Author: kochi <kochi@chromium.org>
Date: Wed Jun 29 00:53:23 2016

Document/ShadowRoot split of pointerLockElement

As discussed in
https://github.com/w3c/webcomponents/issues/192

document.pointerLockElement should be now shadow-dom aware,
and it gets adjusted to its node tree.

ShadowRoot.pointerLockElement is also added so it should
work similar to how document/ShadowRoot.activeElement works.

BUG= 622584 

Review-Url: https://codereview.chromium.org/2086293004
Cr-Commit-Position: refs/heads/master@{#402625}

[add] https://crrev.com/d148a25d4b552d08fe0971faf9464c17cedc7e8f/third_party/WebKit/LayoutTests/shadow-dom/pointer-lock-in-shadow.html
[add] https://crrev.com/d148a25d4b552d08fe0971faf9464c17cedc7e8f/third_party/WebKit/LayoutTests/shadow-dom/v0/pointer-lock-in-shadow.html
[add] https://crrev.com/d148a25d4b552d08fe0971faf9464c17cedc7e8f/third_party/WebKit/LayoutTests/shadow-dom/v0/pointer-lock-in-shadow2.html
[add] https://crrev.com/d148a25d4b552d08fe0971faf9464c17cedc7e8f/third_party/WebKit/LayoutTests/shadow-dom/v0/pointer-lock-in-shadow3.html
[modify] https://crrev.com/d148a25d4b552d08fe0971faf9464c17cedc7e8f/third_party/WebKit/LayoutTests/virtual/stable/webexposed/global-interface-listing-expected.txt
[modify] https://crrev.com/d148a25d4b552d08fe0971faf9464c17cedc7e8f/third_party/WebKit/LayoutTests/webexposed/global-interface-listing-expected.txt
[modify] https://crrev.com/d148a25d4b552d08fe0971faf9464c17cedc7e8f/third_party/WebKit/Source/core/dom/Document.idl
[modify] https://crrev.com/d148a25d4b552d08fe0971faf9464c17cedc7e8f/third_party/WebKit/Source/core/dom/DocumentOrShadowRoot.h
[modify] https://crrev.com/d148a25d4b552d08fe0971faf9464c17cedc7e8f/third_party/WebKit/Source/core/dom/DocumentOrShadowRoot.idl
[modify] https://crrev.com/d148a25d4b552d08fe0971faf9464c17cedc7e8f/third_party/WebKit/Source/core/dom/TreeScope.cpp
[modify] https://crrev.com/d148a25d4b552d08fe0971faf9464c17cedc7e8f/third_party/WebKit/Source/core/dom/TreeScope.h
[modify] https://crrev.com/d148a25d4b552d08fe0971faf9464c17cedc7e8f/third_party/WebKit/Source/core/frame/UseCounter.h
[modify] https://crrev.com/d148a25d4b552d08fe0971faf9464c17cedc7e8f/third_party/WebKit/Source/core/page/PointerLockController.cpp
[modify] https://crrev.com/d148a25d4b552d08fe0971faf9464c17cedc7e8f/tools/metrics/histograms/histograms.xml

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/7108fffd85ed6c21acdb88991b48395ae2cbb822

commit 7108fffd85ed6c21acdb88991b48395ae2cbb822
Author: kochi <kochi@chromium.org>
Date: Mon Jul 04 01:16:09 2016

Fix the testharness async test API usage

This fixes the usage of testharness.js async_test API usages
in pointer lock test for Shadow DOM.

BUG= 622584 

Review-Url: https://codereview.chromium.org/2114783003
Cr-Commit-Position: refs/heads/master@{#403626}

[modify] https://crrev.com/7108fffd85ed6c21acdb88991b48395ae2cbb822/third_party/WebKit/LayoutTests/shadow-dom/pointer-lock-in-shadow.html
[modify] https://crrev.com/7108fffd85ed6c21acdb88991b48395ae2cbb822/third_party/WebKit/LayoutTests/shadow-dom/v0/pointer-lock-in-shadow.html
[modify] https://crrev.com/7108fffd85ed6c21acdb88991b48395ae2cbb822/third_party/WebKit/LayoutTests/shadow-dom/v0/pointer-lock-in-shadow2.html
[modify] https://crrev.com/7108fffd85ed6c21acdb88991b48395ae2cbb822/third_party/WebKit/LayoutTests/shadow-dom/v0/pointer-lock-in-shadow3.html