mirrors/electron
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions 1

Send history operations as asynchronous messages

Browse source 
Sending as sync message will cause weird results for
NavigationController
This commit is contained in:
Cheng Zhao 2015-05-11 16:03:25 +08:00
parent d1545a64ae
commit 82ffa4d2b1
3 changed files with 13 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

13
atom/renderer/lib/override.coffee
View file

@ -74,15 +74,16 @@ window.confirm = (message, title='') ->
window.prompt = ->
throw new Error('prompt() is and will not be supported.')
# Forward history operations to browser.
window.history.back = ->
remote.getCurrentWebContents().goBack()
window.history.forward = ->
remote.getCurrentWebContents().goForward()
# Simple implementation of postMessage.
window.opener =
postMessage: (message, targetOrigin='*') ->
ipc.send 'ATOM_SHELL_GUEST_WINDOW_MANAGER_WINDOW_OPENER_POSTMESSAGE', message, targetOrigin
ipc.on 'ATOM_SHELL_GUEST_WINDOW_POSTMESSAGE', (message, targetOrigin) ->
window.postMessage message, targetOrigin
# Forward history operations to browser.
sendHistoryOperation = (args...) ->
ipc.send 'ATOM_SHELL_NAVIGATION_CONTROLLER', args...
window.history.back = -> sendHistoryOperation 'goBack'
window.history.forward = -> sendHistoryOperation 'goForward'