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
x/website: Table of contents in the language specification missing #49204
Comments
Safari 15.0 shows it fine for me on my iMac running 11.6. |
My apologies, I should have checked more carefully. I'm certain I have seen this on Big Sur before, but I cannot verify this anymore. However, I don't see this problem anymore on Monterey, so maybe I'm wrong. But I have also verified this on Catalina just now, and there the problem still exists, I don't see a table of contents there. |
The table of contents is generated client side with js, are there any errors when it doesn't render? |
I see the following messages in the JavaScript console: [Info] Content blocker prevented frame displaying https://golang.org/ref/spec from loading a resource from https://ssl.google-analytics.com/ga.js (spec, line 6944) |
It targets this line, which certainly appears to exist https://github.com/golang/website/blob/master/_content/site.tmpl#L45 (and works everywhere else). Given that you said it was no longer reproducible on your original machine, could it just be safari's aggressive local caching? (the class name changed a month ago) |
I have checked on Catalina again, and emptied caches through the hidden Develop menu in Safari, and now the table of contents indeed show up. I wasn't aware that Safari is so aggressive at caching, I always thought that a reload should do the trick. Thanks a lot for the help, very much appreciated!!! |
Closing as this appears to be a browser issue |
Since recently, I don't see the table of contents for the language specification at https://golang.org/ref/spec anymore. This is for Safari 15 on macOS. (I see this in Catalina, Big Sur, and Monterey.) On Chrome, the table of contents shows up fine.
It would be great if this could be fixed.
The text was updated successfully, but these errors were encountered: