Windows 10 Spartan/Edge browser should not disable asm.js optimizations when observing the console log view of the page.

By design Issue #5201302

Details

Created
Oct 27, 2015
Privacy
This issue is public.
Reports
Reported by 0 people

Sign in to watch or report this issue.

Steps to reproduce

URL:

Repro Steps:

Navigate to any page with asm.js content, e.g. https://kripken.github.io/Massive/ and try to view the console while the test is running.

Expected Results:

The browser should operate the same independent of whether web console is open or not, since it is very counterintuitive for having the console open to potentially change how the page is run. Running asm.js content without asm.js optimizations enabled easily can mean a performance difference of 5x or more, so it would be best not to disable asm.js when the console window is open. Otherwise debugging asm.js specific bugs, or pages with asm.js content in general can be quite impossible.

Actual Results:

Dev Channel specific:

Yes

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Rico M.”

      Changed Assigned To to “ChakraTriage”

      Changed Assigned To from “ChakraTriage” to “Dan M.”

      Changed Assigned To from “Dan M.” to “IE S.”

      Changed Status to “By design”

    • Hi Brahma, it seems this is a request that we do not disable asm.js when opening F12, but that’s the design that Chakra requested. We do show what to do to to get asm.js back – hit disconnect and optionally refresh the page.

       

       

      Show more

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

    Sign in