Extension content scripts leak exceptions

Fixed, flighted Issue #7698441

Details

Created
May 26, 2016
Privacy
This issue is public.
Fixed in build #
15004
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

Install any extension that throws properly caught exceptions from content scripts (JQuery does this by design, for example)
Navigate to any page
Open F12

Expected

The exceptions do not appear in the console since they are properly caught within the content script

Actual

Exceptions appear since content scripts in Edge leak exceptions (even if they’re properly caught) all the way to the page context

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Akshay P.”

      Changed Assigned To from “Akshay P.” to “Scott L.”

      Changed Status to “Site Outreach”

      Changed Assigned To from “Scott L.” to “Mandeep S.”

      Changed Title from “: Refresh Page Error when using Pocket Extension on sway.com” to “browser.tabs.executeScript leaks exceptions”

      Changed Assigned To from “Mandeep S.” to “Scott L.”

      Changed Steps to Reproduce

      Changed Assigned To from “Scott L.” to “Sermet I.”

      Changed Assigned To from “Sermet I.” to “Scott S.”

      Changed Status from “Site Outreach” to “Confirmed”

      Changed Status from “Confirmed” to “In progress”

      Changed Steps to Reproduce

      Changed Title from “browser.tabs.executeScript leaks exceptions” to “Extension content scripts leak exceptions”

      Changed Steps to Reproduce

      Changed Assigned To from “Scott S.” to “Brandon W.”

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

    • This bug has been resolved and the fix will appear in Windows Insider Preview builds in the new year. Once the fix has flighted, I’ll spin up the process for back-porting this to Anniversary Update builds as well and will update this bug with more information.

    • Microsoft Edge Team

      Changed Assigned To from “Brandon W.” to “Mandeep S.”

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

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

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

    Sign in