Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
"Plug-in is blocked" message doesn't draw correctly
https://bugs.webkit.org/show_bug.cgi?id=149741 <rdar://problem/22920949> Patch by Conrad Shultz and Ricky Mondello. Patch by Ricky Mondello <rmondello@apple.com> on 2015-10-03 Reviewed by Anders Carlsson. Source/WebCore: No new tests are added. Add PluginData API to check whether a MIME type is supported, regardless of plug-in visibility. * plugins/PluginData.cpp: (WebCore::PluginData::getWebVisibleMimesAndPluginIndices): Adopt getMimesAndPluginIndiciesForPlugins. (WebCore::PluginData::getMimesAndPluginIndices): Added. (WebCore::PluginData::getMimesAndPluginIndiciesForPlugins): Essentially factored out of getWebVisibleMimesAndPluginIndices. (WebCore::PluginData::supportsMimeType): Added. Somewhat similar to preexisting supportsWebVisibleMimeType. * plugins/PluginData.h: Declare supportsMimeType. Source/WebKit2: If a WebKit client sets plug-in X to not be visible to the web, that doesn't mean we shouldn't consult that plug-in when determining what kind of object type an object is. Properly classifying a non-web-visible Netscape plug-in as such allows its bounds to properly measured, allowing it to be drawn properly. * WebProcess/WebCoreSupport/WebFrameLoaderClient.cpp: (WebKit::WebFrameLoaderClient::objectContentType): Use PluginData's supportsMimeType, rather than its supportsWebVisibleMimeType, when determining the ObjectContentType for a MIME type on a url. Canonical link: https://commits.webkit.org/167895@main git-svn-id: https://svn.webkit.org/repository/webkit/trunk@190547 268f45cc-cd09-0410-ab3c-d52691b4dbfc
- Loading branch information
1 parent
3f6b1e9
commit 000fc6e
Showing
5 changed files
with
70 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters