An extension BG script that is turned off when Edge starts doesn't start until after its browserAction is clicked

Fixed Issue #10087452

Details

Created
Dec 6, 2016
Privacy
This issue is public.
Reports
Reported by 0 people

Sign in to watch or report this issue.

Steps to reproduce

Additional (Updated 12/14) repro steps;

I spun up an RS_EDGE 161213 build, and was able to repro by
performing the following steps

Install AdBlock for Edge
from the Windows Store

Enable the extension and
confirm the first run page opens (BG script runs on first install
completely fine)

Disable the extension

Close Edge

Reopen Edge

Navigate to
http://simple-adblock.com/faq/testing-your-adblocker/

 and confirm that both boxes are red (since AB is disabled)

Re-enable AB

Refresh the page

Other repro steps:

Install any extension that has a browserAction, but not a popup
Turn the extension off
Close Edge
Re-open Edge
Turn the extension on

Expected

The extension’s background script starts immediately

Actual

The extension’s background script only starts once the browserAction is clicked. It then takes a second click to invoke the onClicked.addListener()

Additional Information

This only repros in RS1. It has been fixed in RS2 builds
Any extension with a browserAction popup does not seem to exhibit this behavior
This repros on early RS1 builds, so my guess is that we shipped like this
If there is no browserAction, there is no way to start the extension’s background script aside from spinning up the background F12 instance

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Chee C.”

      Changed Steps to Reproduce

      Changed Steps to Reproduce

      Changed Title from “An extension that is turned off when Edge starts doesn't start until after its browserAction is clicked” to “An extension BG script that is turned off when Edge starts doesn't start until after its browserAction is clicked”

      Changed Steps to Reproduce

      Changed Status to “Confirmed”

      Changed Assigned To to “Akshay P.”

      Changed Assigned To from “Akshay P.” to “Anushree B.”

      Changed Steps to Reproduce

      Changed Assigned To from “Anushree B.” to “Scott L.”

      Changed Status from “Confirmed”

    •  This is a duplicate of a known issue that will be fixed in upcoming flights in January.

    • Microsoft Edge Team

      Changed Assigned To from “Scott L.” to “Anushree B.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Anushree B.” to “Scott L.”

      Changed Status from “Confirmed” to “Fixed”

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

    Sign in