-
Notifications
You must be signed in to change notification settings - Fork 18k
x/website: anchor links don't seem to work properly anymore #49754
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
Labels
Milestone
Comments
Thanks. The problem is the floating header. It seems OK to me for now to just unfloat the header. I will send a CL for that. |
Change https://golang.org/cl/366974 mentions this issue: |
MK825
added a commit
to MK825/website
that referenced
this issue
Oct 18, 2022
Otherwise anchored links end up scrolling the page so that the thing we want to see is behind the header. We used to have JS cleverness for this, but that broke other parts of the page - in particular, it destroyed any HTML inside <h2> tags and also only applied to <h2> tags - so it was deleted in CL 362499. Let's just be less clever and let the header scroll off the page. That is nicer for viewing content anyway. Fixes golang/go#49754. Change-Id: I14aa9d8e2626d917fbace14d911891777aa6a257 Reviewed-on: https://go-review.googlesource.com/c/website/+/366974 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>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
I think this is a regression from when golang.org was replaced by go.dev in the past week or so.
If I go to https://go.dev/ref/spec#Order_of_evaluation on either Firefox 94.0.2 or Chrome 96.0.4664.45, the anchor link doesn't seem to be working properly, as I don't see the heading I linked to unless I scroll back up.
I imagine this might be related to the banners at the top, as they are what is blocking the view.
Here is roughly what I expected to see:
cc @dmitshur
The text was updated successfully, but these errors were encountered: