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.
This commit is contained in:
parent
524bab530a
commit
a64978b812
4 changed files with 14 additions and 5 deletions
|
@ -104,7 +104,7 @@ void Initialize(v8::Local<v8::Object> exports, v8::Local<v8::Value> unused,
|
|||
dict.SetMethod("setRemoteObjectFreer", &atom::RemoteObjectFreer::BindTo);
|
||||
dict.SetMethod("createIDWeakMap", &atom::api::KeyWeakMap<int32_t>::Create);
|
||||
dict.SetMethod("createDoubleIDWeakMap",
|
||||
&atom::api::KeyWeakMap<std::pair<int32_t, int32_t>>::Create);
|
||||
&atom::api::KeyWeakMap<std::pair<int64_t, int32_t>>::Create);
|
||||
}
|
||||
|
||||
} // namespace
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue