New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setup protocol after ready has already fired #6095

merged 1 commit into from Jun 17, 2016


None yet
3 participants

kevinsawicki commented Jun 16, 2016

Looks like in 1.2.3 browser/api/protocol.js is no longer eagerly required so the properties/methods are missing on it since the ready event on app has already been fired when required later on and so the properties from session.defaultSession.protocol were never copied over to the exports object.

This pull request adds a check app.isReady() to handle this case.

I think it might have been introduced by this line,

Closes #6094


This comment has been minimized.


paulcbetts commented Jun 16, 2016

I feel like in general, the ready event should immediately fire if someone subscribes to it after app is ready, but this fixes the short-term problem at least


This comment has been minimized.


zcbenz commented Jun 17, 2016


@zcbenz zcbenz merged commit 66fe1e4 into master Jun 17, 2016

8 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
electron-linux-arm Build #3463074 succeeded in 41s
electron-linux-ia32 Build #3463075 succeeded in 35s
electron-linux-x64 Build #3463076 succeeded in 123s
electron-mas-x64 Build #1567 succeeded in 6 min 12 sec
electron-osx-x64 Build #1573 succeeded in 5 min 48 sec
electron-win-ia32 Build #571 succeeded in 6 min 17 sec
electron-win-x64 Build #561 succeeded in 6 min 20 sec

@zcbenz zcbenz deleted the protocol-ready-bug branch Jun 17, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment