-
Notifications
You must be signed in to change notification settings - Fork 18k
x/website: clicking "share" on the playground reloads the entire page #49766
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Switching between the built-in examples sort of has the opposite problem. The code does change without a full reload, but the URL doesn't change, so it remains on whatever URL I got from my last click of "share". |
Similar: #49742. But that issue doesn't mention the problem described in the first comment here. |
Yes, apparently I didn't notice that the whole page actually reloaded and assumed it was some sneaky history modification in my issue. It definitely reloads everything and removes the output. |
Change https://golang.org/cl/368014 mentions this issue: |
Mainly the JS invocation was set up wrong. Also add the display box for the share URL back, and style the share URL box and the Go release box the same as the example selector box. Also hide the example box when sharing. This used to happen somewhat accidentally on play.golang.org. Make it intentional. Fixes golang/go#49766. Change-Id: Ib297feff123f6fdabebe24cf868a54874c5afc83 Reviewed-on: https://go-review.googlesource.com/c/website/+/368014 Trust: Russ Cox <rsc@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Jamal Carvalho <jamal@golang.org>
I'm fairly sure this did not happen with the old play.golang.org - it would simply update the URL in the browser bar and in the "share" textbox, but it wouldn't reload the entire page.
I don't lose any code with the reload, but it's still slightly distracting. Particularly since the code takes nearly a second for me to fully render again, so the site becomes unusable while it's doing the presumably unnecessary reload.
The text was updated successfully, but these errors were encountered: