You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
rsc
added
NeedsFix
The path to resolution is known, but the work has not been done.
and removed
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
labels
Nov 24, 2021
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.
Fixesgolang/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>
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: