If there is an external PDF plugin but it's blocked, we should still load in PDFPlugin, with a context menu option to perform the equivalent of the unavailable plugin button (thus allowing the client to unblock the plugin). <rdar://problem/12482452>
Created attachment 221837 [details] patch I hate adding more things to findPlugin and pluginLoadPolicy but it is the most straightforward way to go.
Created attachment 221839 [details] rebase
Comment on attachment 221839 [details] rebase View in context: https://bugs.webkit.org/attachment.cgi?id=221839&action=review > Source/WebKit2/UIProcess/API/C/WKPageLoaderClient.h:396 > + // Version 4. > + WKPageWebGLLoadPolicyCallback webGLLoadPolicy; > + > + // Version 5. > + WKPagePluginLoadPolicyCallback pluginLoadPolicy; I'm not clear if we need to rev for this.
(In reply to comment #3) > (From update of attachment 221839 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=221839&action=review > > > Source/WebKit2/UIProcess/API/C/WKPageLoaderClient.h:396 > > + // Version 4. > > + WKPageWebGLLoadPolicyCallback webGLLoadPolicy; > > + > > + // Version 5. > > + WKPagePluginLoadPolicyCallback pluginLoadPolicy; > > I'm not clear if we need to rev for this. Looks like you’re right.
http://trac.webkit.org/changeset/162629
Part of this was reverted in https://trac.webkit.org/r162883