Bugfix chrome webworker #39
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
June 24, 2015 18:05
The latest Chrome seems to have problems with setting a message-callback with by 'addEventListener'
|
Thanks. 🎉 Will check it tonight and pushing a patch release if working fine. :) |
|
Looking good. Thanks a lot. Will release patch version in a second. :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi Stefan,
since my Chrome updated to Version 43.0.2357.130 m, it had problems connecting the pange with the webworker by addEventListener. The Webworker got never started properly or if it get started, I never returnend any message from it.
So I fixed this tiny issue. I hope you can easily merge this pull request.