Move Document.fullscreenElement to DocumentOrShadowRoot

third_party/WebKit/Source/core/dom/DocumentOrShadowRoot.h

 // Copyright 2016 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #ifndef DocumentOrShadowRoot_h
 #define DocumentOrShadowRoot_h
 
 #include "core/dom/Document.h"
+#include "core/dom/Fullscreen.h"
 #include "core/dom/shadow/ShadowRoot.h"
 #include "core/frame/UseCounter.h"
 
 namespace blink {
 
 class DocumentOrShadowRoot {
  public:
   static Element* activeElement(Document& document) {
     return document.activeElement();
   }
@@ skipping 47 matching lines @@
     // Document and ShadowRoot.
     if (!shadowRoot.isV1())
       return nullptr;
     UseCounter::count(shadowRoot.document(),
                       UseCounter::ShadowRootPointerLockElement);
     const Element* target = shadowRoot.document().pointerLockElement();
     if (!target)
       return nullptr;
     return shadowRoot.adjustedElement(*target);
   }
+
+  static Element* fullscreenElement(Document& document) {
+    return Fullscreen::fullscreenElementForBindingFrom(document);

[foolip, 2016/10/10 12:13:40]

I think it's probably fine to not have a special code path for bindings, better
to have the internal APIs behave like bindings and have internal methods
ignoring shadow boundaries if needed.

[kochi, 2016/10/17 11:14:27]

The motivation I introduced *ForBinding* was that there are some other
users of Fullscreen::fullscreenElementFrom(), and I think what they need
is shadow boundary-agnostic one (the original), and shadow boundary-aware
one is only needed for bindings.

+  }
+
+  static Element* fullscreenElement(ShadowRoot& shadowRoot) {
+    return Fullscreen::fullscreenElementForBindingFrom(shadowRoot);
+  }
 };
 
 }  // namespace blink
 
 #endif  // DocumentOrShadowRoot_h