1544203 - devtools report wrong file:line

Status: UNCONFIRMED

(DevTools :: Debugger, defect, P3)

Description

[Eugen Konkov]

Attachment: correct name of view

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:66.0) Gecko/20100101 Firefox/66.0

Steps to reproduce:

I dynamically load javascript:

$.ajax({
  url      : oop.LibDir +moduleName+ '.js',
  async    : false,
  dataType : 'text',
  success  : function( data ) {
      window.eval( data + "\n//# sourceURL=" + moduleName + ".js");
  },
});

Actual results:

when the target source has syntax error FF does not report correct file when error happened. the line though is correct

When the exception occur at such dynamically loaded code then 'eval' is used for file name at the error message

but the name of the view for this source code is correct also (see attached files)

Expected results:

sourceUrl should be used instead of 'eval'

Comment 1

[Eugen Konkov]

Attachment: correct bahavior of Chrome

Comment 2

[Eugen Konkov]

Attachment: incorrect 'eval' is used instead of TMaitreD.js

Comment 3

[Adrian Florinescu [:aflorinescu]]

Thank you Eugen for the report. Could you please attach a reduced test case to help reproducing the issue?

Comment 4

[Eugen Konkov]

Attachment: del.tar

example

Comment 5

[Eugen Konkov]

you also can make syntax error at hello.js file and see the file:line of error

Comment 6

[Eugen Konkov]

Attachment: modified.tar

modified example

Comment 7

[Eugen Konkov]

Attachment: __.jpg

Comment 8

[yohoho]

modified example https://yohoho.school https://yohoho.me https://yohoho-io.space

Comment 9

[Tanishkavyas]

If you are experiencing issues with DevTools reporting the https://igeopecwebmail.com/ file or line number, it could be due to a number of different factors. Here are some possible solutions to consider:

Check for source maps: If you are using source maps to map your minified or transpiled code back to its original source, make sure that they are correctly configured and up-to-date. Source maps can sometimes cause issues with file and line reporting, so it's important to double-check that they are working correctly.

Clear cache and cookies: DevTools may sometimes cache files https://posteinganginbox.de/ and scripts, which can cause issues with file and line reporting. Clearing your cache and cookies may help resolve the issue.

Restart DevTools: Sometimes, simply restarting DevTools can help clear up any https://portaloffice.pl/
issues with file and line reporting.

Check for code issues: If there are errors or issues with your code, this can also cause problems with file and line reporting. Make sure that your code is valid and error-free, and double-check that there are no issues with file paths or module imports.

Update DevTools: If you are using an older version of DevTools, updating to the latest version may help resolve any issues with file and line reporting.

Report the issue: If none of the above solutions work, it's possible that there may be a bug or issue with DevTools. Reporting the issue to the relevant developer community or support team may help identify and resolve the issue.

By following these steps, you should be able to diagnose and resolve any issues with DevTools https://unitymediawebmail.xyz/ reporting the wrong file or line number.