Send history operations as asynchronous messages
Sending as sync message will cause weird results for NavigationController
This commit is contained in:
parent
d1545a64ae
commit
82ffa4d2b1
3 changed files with 13 additions and 7 deletions
|
@ -1,3 +1,9 @@
|
|||
ipc = require 'ipc'
|
||||
|
||||
# The history operation in renderer is redirected to browser.
|
||||
ipc.on 'ATOM_SHELL_NAVIGATION_CONTROLLER', (event, method, args...) ->
|
||||
event.sender[method] args...
|
||||
|
||||
# JavaScript implementation of Chromium's NavigationController.
|
||||
# Instead of relying on Chromium for history control, we compeletely do history
|
||||
# control on user land, and only rely on WebContents.loadUrl for navigation.
|
||||
|
|
|
@ -29,7 +29,6 @@ module.exports.wrap = (webContents) ->
|
|||
|
||||
# The navigation controller.
|
||||
controller = new NavigationController(webContents)
|
||||
webContents.controller = controller
|
||||
for name, method of NavigationController.prototype when method instanceof Function
|
||||
do (name, method) ->
|
||||
webContents[name] = -> method.apply controller, arguments
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue