1230246 - Breakpoint does not remain on refresh within iframes, only on top level documents

Status: RESOLVED INVALID

(DevTools :: Debugger, defect, P3)

Description

[Greg Whitworth]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2486.0 Safari/537.36 Edge/13.11073

Steps to reproduce:

Went to this site: http://www.thedamageisdone.net/?expref=next-blog
Opened dev tools
Switched to debugger
Inspected the "Followers Box" so that the scripts for the document will show up (it is an iframe)
Under blogger.com -> followers.g I set a breakpoint on line 71
Hit refresh



Actual results:

Breakpoint no longer remains, nor is hit on line 71 of the script


Expected results:

The breakpoint should be hit and allow for debugging

Comment 1

[Nick Fitzgerald [:fitzgen] [⏰PST; UTC-8]]

The query parameters are changing across refreshes, so we don't consider the source the "same" across refreshes. Not sure what the best work around is...

First load: https://www.blogger.com/followers.g?blogID=8604442634625937090&origin=http://www.thedamageisdone.net/&colors=Cgt0cmFuc3BhcmVudBILdHJhbnNwYXJlbnQaBjAwMDAwMCIGMmUyY2IzKgZlOWU5ZTkyBjAwMDAwMDoGMDAwMDAwQgYyZTJjYjNKBjQxNDE0MVIGMmUyY2IzWgt0cmFuc3BhcmVudA%3D%3D&usegapi=1&jsh=m%3B%2F_%2Fscs%2Fapps-static%2F_%2Fjs%2Fk%3Doz.gapi.en.BdKvQrlUBhI.O%2Fm%3D__features__%2Fam%3DAQ%2Frt%3Dj%2Fd%3D1%2Ft%3Dzcms%2Frs%3DAGLTcCMDpwamiqaJrsCQk8jOr0dEPIwuWQ#id=I0_1449168675315&parent=http%3A%2F%2Fwww.thedamageisdone.net&pfname=&rpctoken=26045034

Second load: https://www.blogger.com/followers.g?blogID=8604442634625937090&origin=http://www.thedamageisdone.net/&colors=Cgt0cmFuc3BhcmVudBILdHJhbnNwYXJlbnQaBjAwMDAwMCIGMmUyY2IzKgZlOWU5ZTkyBjAwMDAwMDoGMDAwMDAwQgYyZTJjYjNKBjQxNDE0MVIGMmUyY2IzWgt0cmFuc3BhcmVudA%3D%3D&usegapi=1&jsh=m%3B%2F_%2Fscs%2Fapps-static%2F_%2Fjs%2Fk%3Doz.gapi.en.BdKvQrlUBhI.O%2Fm%3D__features__%2Fam%3DAQ%2Frt%3Dj%2Fd%3D1%2Ft%3Dzcms%2Frs%3DAGLTcCMDpwamiqaJrsCQk8jOr0dEPIwuWQ#id=I0_1449168715591&parent=http%3A%2F%2Fwww.thedamageisdone.net&pfname=&rpctoken=15849405

Comment 2

[Nick Fitzgerald [:fitzgen] [⏰PST; UTC-8]]

(Note the rpctoken query parameter)

Comment 3

[Jason Laster [:jlast]]

Honza, would you mind investigating?

Comment 4

[Jan Honza Odvarko [:Honza] (always need-info? me)]

Here are my STRs & analysis:

Part I.

0. Open DevTools Toolbox and select the Debugger panel
1. Load http://www.thedamageisdone.net/?expref=next-blog
2. Select an iframe (using the button int the Toolbar, right side): followers.g
3. Select www.bloger.com/followers.g file in the Sources panel
4. Create BP at the first line in nextPage function (107 atm)
5. Click next page (it's localized link) in the iframe
6. BP hits, resume
7. The iframe has been reloaded and:

• The iframe picked in step #3 is no longer selected. The context is the page itself again.
• The www.bloger.com/followers.g file is no longer selected in Source panel (I think it's actually not available there anymore, but should be)
• The www.bloger.com/followers.g source tab is closed

Part II.

8. Select www.bloger.com/followers.g file in the Sources panel again

• You can notice that it has different source (but the same URL in the Sources panel?, does Source panel hides the query params? this seems to be wrong)
• The BP from step #4 is gone, obviously (different URL with different URL params).
• There is no nextPage function, but there is prevPage function

9. Create BP at the first line in prevPage function (106 atm)
10. Click prev page (it's localized link) in the iframe
11. BP hits, resume

• The source stays, BP stays, but doesn't work anymore
• Check out the Sources view, the number of followers.g scripts grows every time you click, they have different URL -> thus BP don't work. Now the URL params are properly displayed.

---

1. It looks like a problem with loosing the current frame => Not debugger related.
2. There is the confusing thing with hiding URL params. The server returns different source & URL params every time and the Sources view seems to be confused => Debugger related.

@Jason, can you see the same results? Could this belong to dbg-sources meta?

Honza

Comment 5

[Jason Laster [:jlast]]

Brian, would you be able to look into this?

Comment 6

[Brian Hackett [Laid off!]]

(In reply to Jason Laster [:jlast] from comment #5)

Brian, would you be able to look into this?

I don't understand what change in behavior is desired from comment 4. When navigating backward and forward in the followers pane the client will show a bunch of followers.g sources, but they have different URL parameters (and the client shows the different URL parameters when there are more than one of them) so they are different sources and need breakpoints to be set differently. When going backward and forward several times a bunch of old followers.g sources will pile up, but those sources correspond to scripts that exist in the server (they won't be GC'ed as long as the devtools are attached) and the client is doing a good job of differentiating them AFAICT.

Comment 7

[Jan Honza Odvarko [:Honza] (always need-info? me)]

Thanks Brian for looking into this! The explanation make sense and I am closing this report.

@gwhit: feel free to reopen or file new one if you feel like there is still a bug

Thanks,
Honza