Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

console error: cannot call setActive #2037

Closed
diracdeltas opened this issue Jun 2, 2016 · 1 comment
Closed

console error: cannot call setActive #2037

diracdeltas opened this issue Jun 2, 2016 · 1 comment
Milestone
0.10.1dev

Comments

@diracdeltas
Copy link
Member

i sometimes see this error in the console:

web-view.js:424 Uncaught Error: Cannot call setActive because the webContents is unavailable. The WebView must be attached to the DOM and the dom-ready event emitted before this method can be called.
@diracdeltas
Copy link
Member Author

seems to happen always on startup if i have a gmail tab pinned

bridiver added a commit that referenced this issue Jun 2, 2016
@bridiver
Don't schedule a second callback if one is already waiting on `did-at…
b27cc9d 
…tach`

Although the error mentions `dom-ready`, there is actually a timing problem
with that event and the webContents is always set before `did-attach`
updated fix for #2037

auditors: @bbondy, @diracdeltas
@luixxiul luixxiul added this to the 0.10.1dev milestone Jun 3, 2016
@jonathansampson jonathansampson mentioned this issue Apr 24, 2017
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.10.1dev
Development

No branches or pull requests
2 participants
@diracdeltas @luixxiul