diff options
| author | nick@chromium.org <nick@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-02-05 20:12:12 +0000 |
|---|---|---|
| committer | nick@chromium.org <nick@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-02-05 20:12:12 +0000 |
| commit | 5cdd8fd8e343dbaa131256302eb338eeac7eb2aa (patch) | |
| tree | c95bcb8907541f56dfeff6739e17af04ab7cd6f0 /content/renderer/bmp_image_decoder_unittest.cc | |
| parent | f05966bbaca4477d86688492cc49afe8333dadde (diff) | |
| download | chromium_src-5cdd8fd8e343dbaa131256302eb338eeac7eb2aa.zip chromium_src-5cdd8fd8e343dbaa131256302eb338eeac7eb2aa.tar.gz chromium_src-5cdd8fd8e343dbaa131256302eb338eeac7eb2aa.tar.bz2 | |
Under --site-per-process, route input events from parent process to child frames.
The chain of forwarding starts with an event, in blink, that had been not handled by the document node of a swapped-out frame. It comes into the RenderFrameImpl via the forwardInputEvent method of the blink::WebFrameClient interface. A new IPC message FrameHostMsg_ForwardInputEvent is sent from the renderer process of the parent frame to the browser process, where it is handled by the child frame's CrossProcessFrameConnector, which in turn forwards the event to the RWH hosting the child frame, where it's treated as an ordinary input event.
Related blink change: http://codereview.chromium.org/138003011
The code here is modeled after existing code in BrowserPluginGuest.
BUG=305811, 339659
TEST=loading chromium.org in an iframe under --site-per-process; verify hovering and typing into search box works properly
Review URL: https://codereview.chromium.org/130433016
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@249097 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/renderer/bmp_image_decoder_unittest.cc')
0 files changed, 0 insertions, 0 deletions