1374390 - debugger doesn't show line number for error when doing console function calls

Status: RESOLVED INCOMPLETE

(DevTools :: Console, defect)

Description

[Jim Michaels]

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:54.0) Gecko/20100101 Firefox/54.0
Build ID: 20170608105825

Steps to reproduce:

visited a web page which has js functions
called one of the functions which calls a function that has a parameter that is undefined.



Actual results:

TypeError: start is undefined [Learn More]
no line number is given by the debugger like it used to.


Expected results:

filename:lineNumber should be shown on right side.

Comment 1

[Tooru Fujisawa [:arai]]

most likely fixed by bug 1315242 (Firefox 52), but the new console is not yet enabled on non-nightly channel (bug 1308219).

please describe the issue more, to make sure this is really a dupe of bug 1315242.

  1. what's the URL of the "a web page which has js functions" ?
  2. how do you "called one of the functions" ?

Comment 2

[Jim Michaels]

this bug was originated in 54.0, that is an older version bug. when will the fix be applied?

Comment 3

[Jim Michaels]

normally with debugger error messages you see a line numberand column number on the right hand side of the console in pink.
but with this bug, this is not the case. neither the line or column numbers are shown. this happens once in a while, and it frustrates dbeugging.

Comment 4

[Tooru Fujisawa [:arai]]

please provide the information asked above
https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines

Comment 5

[Brian Grinstead [:bgrins]]

Manually testing this with `data:text/html,<script>function foo() { bar; }</script>`, opening the console and calling `foo()`, I do see line numbers (in a local build). It may be a dupe of Bug 1315242 but it's hard to say without clear STR, so going to resolve this. Feel free to reopen if you can reproduce the problem