JavaScript does not execute after opening and closing F12 debugger tools when contained in an iFrame with console.log call

Not reproducible Issue #7942209


Adam F.
Jun 20, 2016
This issue is public.
Found in
  • Microsoft Edge
  • Internet Explorer
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

In the attached example, index.html uses an iframe element to include frame.html.

In frame.html, a simple html button is present with a basic click handler that performs a console.log() call as well as changes the color of the button text to a random color.

  1. Open index.html and click the button several times to see the event handler being executed and verify that the color of the button text changes.
  2. Open F12 debugger, then close F12 debugger.
  3. Again click the button repeatedly and notice this time the color does not change but instead stays on whichever color was used when the F12 debugger window was first opened.

Note: If the debugger window remains open, the JavaScript executes as normal. It only fails after the f12 debugger tool is opened and closed.

This issue was discovered in the context of a much more complex application structure and has been made minimal for your convenience.

Our development team initially encountered an “Unspecified error.” exception and has narrowed down this issue to only occur when contained within an iframe if the executable JavaScript contains a console.log. The same behavior is not reproducible when viewing the frame.html in the browser as a standalone (e.g. not in an iFrame).


2 attachments

Comments and activity

  • Thank you for your feedback and the repro.  We can’t seem to reproduce this issue in IE or Edge on Windows 10 dand Windows 8 using the uploaded frame.html and index.html.  Can you share what version of Windows and IE/Edge browser you are using?  Thanks.

  • Microsoft Edge Team

    Changed Assigned To to “Ibrahim O.”

    Changed Assigned To to “Leo L.”

    Changed Status to “Not reproducible”

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

Sign in