BrowserPlugin/WebView - Move plugin lifetime to DOM

Source/core/frame/FrameView.cpp

Index: Source/core/frame/FrameView.cpp
diff --git a/Source/core/frame/FrameView.cpp b/Source/core/frame/FrameView.cpp
index e379a3674eaba1695d2bce225ccb10061a7e657b..c4d95b25ddddc9e024fc34a9bb27a0c8039ff107 100644
--- a/Source/core/frame/FrameView.cpp
+++ b/Source/core/frame/FrameView.cpp
@@ -241,9 +241,9 @@ FrameView::~FrameView()
 
     ASSERT(m_frame);
     ASSERT(m_frame->view() != this || !m_frame->contentRenderer());
-    RenderPart* renderer = m_frame->ownerRenderer();
-    if (renderer && renderer->widget() == this)
-        renderer->setWidget(0);
+    HTMLFrameOwnerElement* ownerElement = m_frame->ownerElement();
+    if (ownerElement && ownerElement->widget() == this)

[eseidel, 2014/01/07 22:54:28]

I would just ASSERT(ownerElement->widghet() == this) here, no?  If we were
detatched from our owner element we should also ahve cleared our pointer to it,
no?

[wjmaclean, 2014/01/08 14:36:21]

Maybe I'm misunderstanding, but ownerElement has been cleared, wouldn't the
ASSERT seg fault? I (vaguely) recall the reason I wrote it this way is that
sometimes ownerElement is 0x0.

+        ownerElement->setWidget(0);
 }
 
 void FrameView::reset()