Console log statements should walk up the call stack for the source line when the calling frame(s) is marked as library code

Won’t fix Issue #18045530

Details

Created
Jun 26, 2018
Privacy
This issue is public.
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

  1. Browse to http://plnkr.co/edit/3wg4u9HUGXfFH0U7MR7j?p=preview
  2. Check console, note console log “This is awesome” has a source line in log-helper.js
  3. Mark log-helper.js as library code
  4. Stop/Run the demo again
  5. Check the console again

Expect: source line for “This is awesome” log is script.js because log-helper.js was marked as library code
Actual: source line is still indicated in the library code

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “edgedevtoolstri”

      Changed Status to “Confirmed”

      Changed Assigned To from “edgedevtoolstri” to “Mike J.”

      Changed Status from “Confirmed” to “Won’t fix”

    • Hi!

      We have made a decision to scope bug fixing on the current Edge product to critical security and reliability issues, and the minimum necessary to service in-market customers (RS4, RS5 and 19H1), in order to focus on high quality delivery of the new Edge based on open source.  I am resolving this bug Won’t Fix to let you know of this explicitly, instead of simply keeping the bug active. 

      Thanks,
      Zach

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

    Sign in