-
Notifications
You must be signed in to change notification settings - Fork 214
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
Error with tabs.sendMessage when no response #75
Comments
I can't comment on whether this a bug in the polyfill but I've found that you can make the error go away by adding the following to the end of your message handler.
|
Yes, that's what I've done in the Chrome version. But, the goal of the polyfill is to allow web extensions to run unchanged, hence the bug report that it should do this implicitly. |
I have the same issue with |
There are also other browser bugs around the API, the promise returned by Though these bugs should be fixed in browsers. Developers might type check message responses, so the API behavior should not be changed by the polyfill to hide implementation bugs. |
When nothing is returned from the content script, Chrome throws an error. The polyfill should presumably implicitly return something if the content script doesn't, or otherwise suppress this error.
The text was updated successfully, but these errors were encountered: