summaryrefslogtreecommitdiffstats
path: root/views
diff options
context:
space:
mode:
authorbrettw@chromium.org <brettw@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-03-30 19:02:14 +0000
committerbrettw@chromium.org <brettw@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-03-30 19:02:14 +0000
commitb00bbb39365d95b4e8d95302d1e18507997fd1ec (patch)
tree249310a1f5f6675b5ed5fa08895ba971e5fc03c3 /views
parent0f4ffe84d7b3923b78f7a224910d9b913a62de8a (diff)
downloadchromium_src-b00bbb39365d95b4e8d95302d1e18507997fd1ec.zip
chromium_src-b00bbb39365d95b4e8d95302d1e18507997fd1ec.tar.gz
chromium_src-b00bbb39365d95b4e8d95302d1e18507997fd1ec.tar.bz2
Unblock for all plugin->renderer messages to preserve the ordering for plugin
calls. This comes up if the renderer sent a sync message (say mouse down) and then the plugin responds by doing some setup with async messages (say configuring a URLRequest), and then issuing that request via a sync call (say PPB_Flash.Navigate). Without this, the navigate will be processed before the async messages because the renderer is currently blocked waiting for its own sync message to respond. This will cause reentrancy in the renderer. TEST=Flash BUG=none Review URL: http://codereview.chromium.org/6708125 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@79873 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'views')
0 files changed, 0 insertions, 0 deletions