Content scripts context doesn't implement browser.runtime.onConnect

Issue #7517735


May 10, 2016
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 5 people

Sign in to watch or report this issue.

Steps to reproduce

Try to use browser.runtime.onConnect inside injected/content script

Is not implemented as of 14342

Any plans


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Status to “Not reproducible”

    • Thanks for the feedback! This API should be available in the flight that was just released (14342).

      In general, a high level view of the extensions API roadmap is here:

    • This API is not available inside content scripts!

      See screenshot

    • Microsoft Edge Team

      Changed Steps to Reproduce

      Changed Status from “Not reproducible”

    • Reactivating for the team to take another look.

    • Microsoft Edge Team

      Changed Assigned To to “Sermet I.”

      Changed Assigned To from “Sermet I.” to “Chee C.”

      Changed Assigned To from “Chee C.” to “Akshay P.”

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

      Changed Status to “Confirmed”

      Changed Status from “Confirmed” to “By design”

    • Is this being worked on? I see that status has been changed to “By design” but both Firefox WebExtension API and Chrome Extension API have it implemented.

    • Microsoft Edge Team

      Changed Status from “By design”

    • That was an incorrect resolution. This work is on the backlog but will not make the initial stable release of extensions in Edge this summer.

    • Hi, any update on this issue?

    • The feature task tracking this work was recently completed. The change will make it’s way into Insider flights in the next few weeks.

    • Hello Charles,

      I’m currently running Microsoft Edge 38.14393.0.0 and it’s still not available.
      Are there any concrete dates/versions regarding this feature?

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

    Sign in