x/playground: firing "load" event too early #56953
Labels
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Comments
|
For context: I stumbled on this when trying to scrap source code and screenshots of code that I stored in various playgrounds, from their permalinks. When load is fired, the source code area is still empty.
For the Go playground specifically, an easy workaround for me (instead of using a headless browser such as chromedp) is to extract the snippet ID from the URL e.g. |
|
The same content is available by appending |
|
That's amazing, thanks for the tip! |
seankhliao
added
the
NeedsInvestigation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of Go are you using (
go version)?go1.19.2
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env)?Just the web playground
What did you do?
Open Google Chrome
Open the DevTools panel, on the tab Networks
Load the permalink of a playground program e.g. https://go.dev/play/p/ejOfDs_Hg9
Filter the network tab on the snippet ID:
ejOfDs_Hg9What did you expect to see?
The red vertical line (load event) should be after the snippet source code request has finished loading, in the waterfall
What did you see instead?
The red vertical line (load event) is before the snippet source code request, in the waterfall
This is a nit, not a serious bug!
Currently, opening a given program's playground permalink loads the page layout HTML, then the JS, then the actual main content which is the program source code. We may want to honor the doc of the load event: "is fired when the whole page has loaded, including all dependent resources".
The text was updated successfully, but these errors were encountered: