Closed Bug 1265327 Opened 9 years ago Closed 6 years ago

Event popup's "Open in Debugger" does not jump to correct file for source mapped (minified) js files

Categories

(DevTools :: Inspector, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: nachtigall, Unassigned)

References

Details

(Whiteboard: [btpp-fix-later][dt-q])

Attachments

(1 file)

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0 Build ID: 20160407164938 Steps to reproduce: 1. Open Devtools 2. Go to a page which uses minified JS with a source map 3. Hover over a DOM node which has an JS event attached 4. Click on the "ev" button to see the event popup 5. Click on "Open in Debugger" Actual results: Jumps to the last open file and position in Debugger panel. Expected results: Jump to the correct line in correct file for the function shown in the event popup
Component: Untriaged → Developer Tools: Inspector
See Also: → 1264964
Inspector bug triage. Filter on CLIMBING SHOES. If the inspector makes you jump to a wrong file this is pretty bad. Feature is broken -> P2 ni? myself to verify the bug
Flags: needinfo?(jdescottes)
Priority: -- → P2
Whiteboard: [btpp-fix-later]
Flags: needinfo?(jdescottes)
I'm fixing source-maps in the event popup in bug 1361853.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Sorry, wrong bug.
Product: Firefox → DevTools

Looks like it was duped by accident and never re-opened. Mike; could you help here to confirm if the work is in Debugger or the Inspector? It is important to finally get to a good level of source maps and this issue keeps popping up in feedback and breaks the smooth interplay between panels.

Martin, we are still confirming if this is an issue in the Debugger or Inspector – but would this make a good bug for the quality backlog?

Status: RESOLVED → REOPENED
Ever confirmed: true
Flags: needinfo?(mratcliffe)
Flags: needinfo?(mbalfanz)
Resolution: DUPLICATE → ---

Agreed, I added it to the backlog. Though if it's not an inspector bug we may remove it again from there.

Flags: needinfo?(mbalfanz)
Whiteboard: [btpp-fix-later] → [btpp-fix-later][dt-q]

Tom fixed this in bug 1333352 and it works just fine now.

Assignee: nobody → mratcliffe
Status: REOPENED → RESOLVED
Closed: 8 years ago6 years ago
Flags: needinfo?(mratcliffe)
Resolution: --- → WORKSFORME
Attached image image.png

Mike, can you confirm where this would work?

This is not working for me on sites with source maps, send.firefox.com, reddit.com or github.com . All events link to the same file and position; even though the event handler inline preview shows the correct handler source.

Flags: needinfo?(mratcliffe)

(In reply to :Harald Kirschner :digitarald from comment #7)

Created attachment 9051776 [details]
image.png

Mike, can you confirm where this would work?

This is not working for me on sites with source maps, send.firefox.com, reddit.com or github.com . All events link to the same file and position; even though the event handler inline preview shows the correct handler source.

It seems like we at the very least have edge cases... re-opening.

Status: RESOLVED → REOPENED
Flags: needinfo?(mratcliffe)
Resolution: WORKSFORME → ---
Assignee: mratcliffe → nobody

Made a simpler test case: https://amusing-dove.glitch.me/

STR:

  1. Open Devtools
  2. Inspect the first button which has an JS event attached
  3. Click on the "ev" button to see the event popup
  4. Click on "Open in Debugger" icon

I am unsure about this having just edge cases. I have not seen it working for any source mapped case.

To clarify:

Inline code preview in the events panel works and shows the correct handler. Resolving the filename and location works and shows the original location.

Clicking the link to the Debugger is what isn't working and send to the wrong file (generated file instead of original) with the correct original location. In the example, the original location of index.js:13 jumps to the generated file client.js:13.

I'm going to close this in favor of https://bugzilla.mozilla.org/show_bug.cgi?id=1538397 since this seems like a new regression separate from the older issue.

Status: REOPENED → RESOLVED
Closed: 6 years ago6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: