diff options
author | piman@chromium.org <piman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-11-22 02:04:22 +0000 |
---|---|---|
committer | piman@chromium.org <piman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-11-22 02:04:22 +0000 |
commit | 61176efeb97b4c36ff83abf71d611a9efbfc90e2 (patch) | |
tree | 519979f0eb8bfed7afe8e2fcec48f718297bf447 /chrome_frame | |
parent | 2fa83c40a8fdef0dd07863761674ffb8acf11fd1 (diff) | |
download | chromium_src-61176efeb97b4c36ff83abf71d611a9efbfc90e2.zip chromium_src-61176efeb97b4c36ff83abf71d611a9efbfc90e2.tar.gz chromium_src-61176efeb97b4c36ff83abf71d611a9efbfc90e2.tar.bz2 |
Remove IsProtocolSupportedForMedia.
scherkus says:
The protocol whitelist (added in r26746) was originally required to prevent issuing requests to the resource loader bridge that it didn't support (i.e., data://). To complicate matters there were protocols such as chrome-extension:// that required the embedder to override. None of this is required anymore since we switched to using Chromium WebKit API's resource loader in r69429.
BUG=98755
TEST=Chrome, DRT, test_shell, test_shell_tests
Review URL: http://codereview.chromium.org/8616008
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@111075 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome_frame')
0 files changed, 0 insertions, 0 deletions