summaryrefslogtreecommitdiffstats
path: root/ppapi/proxy/ppb_font_proxy.cc
diff options
context:
space:
mode:
authoragl@chromium.org <agl@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-02-08 16:17:23 +0000
committeragl@chromium.org <agl@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-02-08 16:17:23 +0000
commit9941cf535dfdf8a7a81de38e71803d7095ba703e (patch)
tree75c152cb1ef3e2107377fa534394df281e08d38b /ppapi/proxy/ppb_font_proxy.cc
parent7024d3eea1d8328883736f5cd3cbef480aa0e740 (diff)
downloadchromium_src-9941cf535dfdf8a7a81de38e71803d7095ba703e.zip
chromium_src-9941cf535dfdf8a7a81de38e71803d7095ba703e.tar.gz
chromium_src-9941cf535dfdf8a7a81de38e71803d7095ba703e.tar.bz2
Add debug logging for mixed scripting.
Our mixed scripting can be very difficult to debug when the offending request comes from nested iframes and the like because the issue won't show up in the Javascript console for the page. This also occurs if a redirect page loads mixed scripting. This change cleans up a previous change (r71881) now that the WebKit side of this has landed, and logs mixed scripting issues to the debug log (when logging is enabled). BUG=none TEST=Run with --enable-logging and go to a site with mixed scripting. Confirm that a debug entry appears in the chrome_debug.log. Review URL: http://codereview.chromium.org/6246149 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@74119 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ppapi/proxy/ppb_font_proxy.cc')
0 files changed, 0 insertions, 0 deletions