runtime.sendMessage behaves differently than Chrome/Firefox

Fixed, flighted Issue #8504730

Details

Author
Eric L.
Created
Aug 16, 2016
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
38.14393
Fixed in build #
15002
Reports
Reported by 2 people

Sign in to watch or report this issue.

Steps to reproduce

Sending a message to an extension popup from an extension content script silently fails in Edge if a null parameter is provided.

Working in Chrome/Firefox:

const obj = {cLinks: cLinks, unsecure: arrUnsecure };
chrome.runtime.sendMessage(obj, null);

Required to work in Edge:

const obj = {cLinks: cLinks, unsecure: arrUnsecure };
chrome.runtime.sendMessage(obj);

My assumption here is that the failing code is hitting the wrong overload of sendMessage in Edge (e.g. it’s stringify’ing obj and then treating that as the target extension ID string, then sending a null object as the content of the message?)

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Brad E.”

      Changed Assigned To to “Sebastian P.”

      Changed Assigned To from “Sebastian P.” to “Cameron S.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Cameron S.” to “Akshay P.”

      Changed Assigned To from “Akshay P.” to “Arif S.”

      Changed Assigned To from “Arif S.” to “Snehita P.”

      Changed Status from “Confirmed” to “In code review”

      Changed Status from “In code review” to “In progress”

      Changed Status from “In progress” to “Fixed, not yet flighted”

      Changed Status from “Fixed, not yet flighted” to “Fixed, flighted”

    • Where do I find info in which build was this fixed?

    • Microsoft Edge Team

      Changed Assigned To to “Vasanth C.”

    You need to sign in to your Microsoft account to add a comment.

    Sign in