-
tomernic authored
Reviewed by John Sullivan. <rdar://problem/4480186> Give WebKit plugins access to their own DOM element * bridge/mac/WebCoreFrameBridge.h: Added DOMElement: parameter to -viewForPluginWithURL:attributeNames:attributueValues:MIMEType: * bridge/mac/FrameMac.h: * bridge/mac/FrameMac.mm: (WebCore::FrameMac::createPlugin): Added "element" parameter; wrap element in DOMElement and pass up to the bridge. * page/Frame.h: Added "element" parameter to createPlugin(). * page/Frame.cpp: (WebCore::Frame::loadPlugin): Get the plugin's DOM element and pass to createPlugin(). WebKit: Reviewed by John Sullivan. <rdar://problem/4480186> Give WebKit plugins access to their own DOM element This does not fix <rdar://problem/4480187> Give Netscape plugins access to their own DOM element -- we're not going to use the ObjC DOM API for that, but rather the NP bindings API. * Plugins/WebPluginPackage.m: Declared WebPlugInContainingElementKey. This is not a new plugin argument -- it's been in our public headers since all along, but has never been concretely declared -- plugins that referenced it would not link. * WebCoreSupport/WebFrameBridge.m: (-[WebFrameBridge pluginViewWithPackage:attributeNames:attributeValues:baseURL:DOMElement:]): Added DOMElement parameter, which is now included in the plugin arguments dictionary. (-[WebFrameBridge viewForPluginWithURL:attributeNames:attributeValues:MIMEType:DOMElement:]): ditto * WebKit.exp: Export WebPlugInContainingElementKey. git-svn-id: http://svn.webkit.org/repository/webkit/trunk@14185 268f45cc-cd09-0410-ab3c-d52691b4dbfc
3b1b8029