Move Document.fullscreenElement to DocumentOrShadowRoot

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

Index: third_party/WebKit/Source/core/dom/DocumentOrShadowRoot.h
diff --git a/third_party/WebKit/Source/core/dom/DocumentOrShadowRoot.h b/third_party/WebKit/Source/core/dom/DocumentOrShadowRoot.h
index 8a31e5ef3be2349075da2ff54049acf8ae344875..4b4c1b6499096546fd2561c3f0f3080aab532b1d 100644
--- a/third_party/WebKit/Source/core/dom/DocumentOrShadowRoot.h
+++ b/third_party/WebKit/Source/core/dom/DocumentOrShadowRoot.h
@@ -6,6 +6,7 @@
 #define DocumentOrShadowRoot_h
 
 #include "core/dom/Document.h"
+#include "core/dom/Fullscreen.h"
 #include "core/dom/shadow/ShadowRoot.h"
 #include "core/frame/UseCounter.h"
 
@@ -73,6 +74,14 @@ class DocumentOrShadowRoot {
       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