Setup:
A chrome.runtime.onMessage listener attached on the top frame which sends no response, and another listener attached on a frame which sends a response. The background page sends a message to the tab.
What happens:
The top frame listener is invoked and returns undefined. A response is returned to the background sendMessage call.
What should happen:
The listener on attached on a frame should be invoked after the top frame listener and checked for either a response or returning true with an intention to respond asynchronously and only then a response should be returned to the background page.
adomasven
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
UTF-8 characters in JS code strings such as ✕ or ’ are not handled properly and come out wrong when displayed/printed.
The spec - https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/webRequest/onHeadersReceived specifies a type property:
type webRequest.ResourceType. The type of resource being requested: for example, "image", "script", "stylesheet".
My webRequest.headersReceived handlers for top frame receive a random number at details.frameId instead of 0 as per the spec.
I have a webRequest.headersReceived listener on my extension and while Chrome and Firefox correctly calls the listener for 302 redirects with intermediate URLs, Safari does not.