console.log line numbers in extension content scripts are off by one

Fixed Issue #13413556


V S.
Aug 24, 2017
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Fixed in build #
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

In the attached test case, console.log in content.js will log line 2, even though it’s at line 1. background.js logs the correct line number.

diagnosticsScript.getStackTrace normally gives us 0-index based numbers, but from content scripts we seem to be getting 1-based line numbers instead, which throws off our logic in console remote.

Since getStackTrace is a DiagOM API, the bug is probably in there.


Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “James M.”

    Changed Assigned To to “”

    Changed Assigned To from “” to “James M.”

    Changed Assigned To to “”

    Changed Assigned To from “” to “Jeff F.”

    Changed Status to “Confirmed”

    Changed Steps to Reproduce

    Changed Assigned To from “Jeff F.” to “Mike J.”

    Changed Assigned To from “Mike J.” to “Jordan B.”

    Changed Status from “Confirmed” to “Fixed”

  • Hello,

    Thank you for providing this information about the issue. We are pleased to report this feature is fixed in Edge and will be available in an upcoming Insider Preview build.

    Best Wishes,
    The MS Edge Team

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

Sign in