562356 - Report error locations on dynamically created script tags with inline code

Status: RESOLVED INVALID

(DevTools :: Console, defect, P3)

Description

[Hans Schmucker]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.3a5pre) Gecko/20100427 ( LIKE Firefox/3.6.3 )
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.3a5pre) Gecko/20100427 ( LIKE Firefox/3.6.3 )

When a script that has been inserted dynamically into the DOM (by creating a script/textNode pair, for example while using a dynamic preprocessor) tries to report an error, the location of the error is unknown and it is difficult to find the actual position.

It would be immensely helpful if Firefox could instead point to the content of the script tag. One example could be creating a data url containing the textContent of the node and reporting the location of the data url as location error.

Reproducible: Always

Steps to Reproduce:
1. Open the given data url
2. Watch the error console for "np is not defined"
Actual Results:  
No location is given for the error. Clicking the error just takes you to the hosting document.

Expected Results:  
Error location should be given as line inside the script node's text content. Clicking should take you to a document containing the content of the node's text.

Comment 1

[Kevin Dangoor]

I'm not certain it will make the difference but there is a lot of additional logging work going on in bug 606498 that might possibly make the difference here. Otherwise, I agree that this would be a nice improvement.

Comment 2

[Hallvord R. M. Steen [:hallvors]]

So this is probably the main reason the debugger gets into confusing states for me on certain websites.. At least symptoms match what I see with this TC. I'd love to get this fixed!

Comment 3

[Nicolas Chevobbe [:nchevobbe]]

STR from Comment 0 does show a location, and clicking on it takes you to the debugger, so I'm assuming the issue is no more.