This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
it would be nice if somehow js could let me know what line number and file from the caller caused the problem. it would make my debugging tremendously easier. I think it would help a lot of people who develop web pages. something like this could be a predefined variable of some kind. thanks. this could mean examining the previous item on the call stack I suppose. the idea is that, within the function call, I could maybe have access to the caller's function name, filename, and line number within the called function somehow. as things are now, some debugger messages are pretty incomprehensible. I get messages about scripts I did not include on my site, and error messages I don't understand because they are specific to some package somewhere (and not documented well). having these 3 pieces of information allows them, and me, to write my libraries in a way that helps the web programmer/designer fix problems without head scratching, they can get the error message form the console.log with the offending line# from the specific file they wrote, and jump right to it and fix the problem. it's a time saver.
change to enhancement.
RE: comment 1 where it says "the idea is that, within the function call, I could maybe have access to the caller's function name, filename, and line number within the called function somehow." could be rewritten more clearly as "the idea is that, within the callee (the function called), I could have access to the caller's function name, filename, and line number within the called function somehow." example: let's say in my file abc.html I am using the library xyz.js <script src="/xyz.js"></script> <script> var x=xyz("123",5); </script> within xyz(), it could console.log() line 20 in file abc.html (or some other case may be that something is being called within a js file) and the calling function is an empty string since there is no parent.
This is outside the scope of the JavaScript / Web ECMAScript spec. See <http://javascript.spec.whatwg.org/#goals>. To propose new features to the ECMAScript language, please file a bug on https://bugs.ecmascript.org/.