summaryrefslogtreecommitdiffstats
path: root/content/renderer/plugin_channel_host.h
diff options
context:
space:
mode:
authorananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-09-08 17:27:01 +0000
committerananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-09-08 17:27:01 +0000
commita1127f8b9d0102ca41437b7927f36e89268a80c2 (patch)
tree3cfdd4d882beba4808023faed1282e9200695d5a /content/renderer/plugin_channel_host.h
parent879145edcef7d2ada4b3da23b977817758eeeeec (diff)
downloadchromium_src-a1127f8b9d0102ca41437b7927f36e89268a80c2.zip
chromium_src-a1127f8b9d0102ca41437b7927f36e89268a80c2.tar.gz
chromium_src-a1127f8b9d0102ca41437b7927f36e89268a80c2.tar.bz2
Move the ViewMsg_FPS and ViewHostMsg_FPS IPC messages out of content to chrome as these are sent and processed by
chrome. These messages are now prefixed with "Chrome" To handle the ChromeViewMsg_GetFPS message in the ChromeRenderViewObserver object we need to expose the value of the filtered_time_per_frame member in the RenderWidget class. Added a getter to achieve that. Continuing changes to ensure that IPCs don't span across content and chrome. BUG=87335 Review URL: http://codereview.chromium.org/7754004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@100178 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/renderer/plugin_channel_host.h')
0 files changed, 0 insertions, 0 deletions