Thiago de Arruda a64978b812 Use the routing id on api::WebContents::GetID ...

The sandbox option allows multiple webContents in one renderer process, so using
the only the renderer id to identify WebContents instances is no longer an
option.

WebContents::GetID now returns a 64-bit integer, which is composed of both the
process id(high 32), and the RenderViewHost routing id(low 32). Also add a
`GetProcessID` that retrieves the renderer process id, a requirement in some of
our javascript code.

2016-09-27 06:01:47 -03:00

..

api

Add support for native chromium popups on sandboxed renderers.

2016-09-27 06:01:46 -03:00

chrome-extension.js

Use the routing id on api::WebContents::GetID

2016-09-27 06:01:47 -03:00

desktop-capturer.js

Remove returns from event listeners

2016-05-19 15:28:08 -07:00

guest-view-manager.js

Add a guestinstance attribute to webviews reflecting their current guest

2016-09-09 10:32:05 -07:00

guest-window-manager.js

Add support for native chromium popups on sandboxed renderers.

2016-09-27 06:01:46 -03:00

init.js

Require Buffer explicitly instead of relying on global

2016-09-08 10:17:06 -07:00

objects-registry.js

clear the storage for the webContentsId when the render view is deleted

2016-08-15 21:53:58 -07:00

rpc-server.js

Add browser side support for reading files from renderer.

2016-09-27 06:01:46 -03:00