Issue
When sphinx-gallery generates a gallery of examples, you can navigate to examples by either clicking on the left-hand side menu or by clicking on the tiles in the gallery. Here's a screenshot of what that looks like on sphinx-gallery's own documentation.

You would expect both links to go to the same place, but this is not the case. The sidebar link for the "Plotting sin" example goes to:
https://sphinx-gallery.github.io/stable/auto_examples/plot_0_sin.html
while clicking on the tile takes you to:
https://sphinx-gallery.github.io/stable/auto_examples/plot_0_sin.html#sphx-glr-auto-examples-plot-0-sin-py
These deliver different user experiences - the former is what you'd expect, while the latter has the page scrolled down to the title. This means that users who click the latter link are unable to see sphinx-gallery's note about downloading example code or running in Binder.

Solution
I'd like to change the tile link so that both go to:
https://sphinx-gallery.github.io/stable/auto_examples/plot_0_sin.html
This should only require modifying sphinx_gallery/backreferences.py, but I'd like @larsoner to first confirm that this is a bug and not intended behavior before I make a PR.
Issue
When sphinx-gallery generates a gallery of examples, you can navigate to examples by either clicking on the left-hand side menu or by clicking on the tiles in the gallery. Here's a screenshot of what that looks like on sphinx-gallery's own documentation.
You would expect both links to go to the same place, but this is not the case. The sidebar link for the "Plotting sin" example goes to:
while clicking on the tile takes you to:
These deliver different user experiences - the former is what you'd expect, while the latter has the page scrolled down to the title. This means that users who click the latter link are unable to see sphinx-gallery's note about downloading example code or running in Binder.
Solution
I'd like to change the tile link so that both go to:
This should only require modifying
sphinx_gallery/backreferences.py, but I'd like @larsoner to first confirm that this is a bug and not intended behavior before I make a PR.