1579994 - Debugger's pretty print shows old script

Status: VERIFIED FIXED

(DevTools :: Debugger, defect, P1)

Description

[Oriol Brufau [:Oriol]]

1. Open web console
2. Run "foo"; debugger;
3. The debugger shows a SOURCEsource77 script with "foo"; debugger;
4. Click 'Pretty print source'. The debugger shows a {} SOURCEsource77 script with

   'foo';
   debugger;
   

5. Resume the debugger, go back to the console.
6. Run "bar"; debugger;
7. The debugger shows a SOURCEsource91 script with "bar"; debugger;
8. Click 'Pretty print source'.

Expected result: the debugger shows a {} SOURCEsource91 script with

'bar';
debugger;

Actual result: the debugger shows the previous {} SOURCEsource77 script with

'foo';
debugger;

Comment 1

[Alex R.]

It looks like the url for both sources created in the console is null, even though they have different source.id values.

In prettyPrint.js ( togglePrettyPrint method), we have:

const url = getPrettySourceURL(source.url);  
const prettySource = getSourceByURL(getState(), url);

if (prettySource) {
      return dispatch(selectPrettyLocation(cx, prettySource));
    }

getSourceByURL returns :formatted for both sources with null URL.

The pretty printed source is created when the first source is passed in, but getSourceByURL returns the same prettySource when we prettyPrint the second source.

Are there other instances (besides creating sources in the console) where we would have two different sources with the same url? Does it make sense to create a unique URL for every source created in the console?

Comment 2

[Jason Laster [:jlast]]

nice find! is there any way we can use source id here?

Comment 3

[Alex R.]

Yeah - I think I found a straightforward solution using the source id to create a URL if the URL is null, which seems to solve the issue.
Later today I'll go ahead and submit a patch for you to check out.

Comment 4

[Alex R.]

Attachment: Bug 1579994 - Handle null source value in prettyPrint r=davidwalsh

use the source id to create a url when pretty printing if the url is null.

Comment 5

[Oriol Brufau [:Oriol]]

(In reply to Alex R. from comment #1)

Are there other instances (besides creating sources in the console) where we would have two different sources with the same url? Does it make sense to create a unique URL for every source created in the console?

Maybe you can have 2 <script> pointing to the same url without caching, and the server response is different each time?

Without knowing much about the debugger, would it be a problem to always use the source id, even if there is an url? Seems more robust

Comment 6

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/cb54e53665de
Handle null source value in prettyPrint r=davidwalsh

Comment 7

[Alexandru Michis [:malexandru]]

https://hg.mozilla.org/mozilla-central/rev/cb54e53665de

Comment 8

[Cristian Fogel [:cfogel]]

Confirmed issue with 70.0 on Windows 10.
Fix verified with 71.0b5 on Windows 10, macOS 10.13, Ubuntu 18.04.