Edge refuses to load content scripts after appending an iframe from another domain

Fixed Issue #12930797


Manuel D.
Jul 25, 2017
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce


Given an extension having a content script running at document_start, appending an iframe to the document.body from the content script will prevent the whole content script from being loaded the next time you reload the page, producing error 80020101.

NOTE: the content script will be correctly loaded if you reload the page again, but the bug will manifest itself on the next reload every time you append an iframe.

NOTE: the bug won’t happen if the iframe src is from the same domain of the page.

NOTE: the bug won’t happen if the content script is loaded at document_end.

Steps to reproduce the issue:

  • Install this minimal extension: https://github.com/Maluen/edge-content-frame-bug (also available in the attachments)
  • Go to https://www.google.com/
  • Open the F12 console, then reload the page, you will see that the “Loading content script” text is correctly logged.
  • In the F12 console. switch to the extension content script context, then execute the following code:
var iframe = document.createElement('iframe');
iframe.src = 'https://www.microsoft.com/';
  • Reload the page

Expected behaviour: the “Loading content script” text should be logged into the console.
Actual behaviour: no text is logged, in fact, the content script isn’t loaded at all, instead Edge will throw a 80020101 error.


Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “James M.”

    Changed Assigned To to “Akshay P.”

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

    Changed Status to “Confirmed”

    Changed Assigned To from “Vasanth C.” to “Scott S.”

    Changed Assigned To from “Scott S.” to “Suyang Z.”

    Changed Status from “Confirmed” to “Not reproducible”

    Changed Status from “Not reproducible” to “Fixed”

  • Hello,

    Thank you for providing this information about the issue. We are pleased to report this feature is fixed in Edge 17083 is available in our Insider Preview build.

    Best Wishes,
    The MS Edge Team

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

Sign in