Move container policy logic to frame owner classes.

third_party/WebKit/Source/core/html/HTMLPlugInElement.cpp

Index: third_party/WebKit/Source/core/html/HTMLPlugInElement.cpp
diff --git a/third_party/WebKit/Source/core/html/HTMLPlugInElement.cpp b/third_party/WebKit/Source/core/html/HTMLPlugInElement.cpp
index ac7486f55342d8957df7796e55916d950660b6b2..0dd8ec293cd9bd4c6b1418483282d8bd9a57f680 100644
--- a/third_party/WebKit/Source/core/html/HTMLPlugInElement.cpp
+++ b/third_party/WebKit/Source/core/html/HTMLPlugInElement.cpp
@@ -268,6 +268,12 @@ bool HTMLPlugInElement::ShouldAccelerate() const {
   return plugin && plugin->PlatformLayer();
 }
 
+Vector<WebParsedFeaturePolicyDeclaration>
+HTMLPlugInElement::ConstructContainerPolicy() const {
+  Vector<WebParsedFeaturePolicyDeclaration> container_policy;

[raymes, 2017/06/12 22:54:26]

nit: perhaps add a comment about why we return an empty policy here

[iclelland, 2017/06/13 14:38:33]

Done, though I actually duplicated the <frame> logic here as well, since it is
really only <iframe> elements that can enable the fullscreen flag, according to
the spec. (And my local tests confirm there really is no way, even in same
origin, to enable fullscreen from an <embed> or <object>-embedded document.)

+  return container_policy;
+}
+
 void HTMLPlugInElement::DetachLayoutTree(const AttachContext& context) {
   // Update the FrameViewBase the next time we attach (detaching destroys the
   // plugin).