Anchor links not working correctly in Chromium (Chrome/Edge)

[rickmed]

URL:

https://nodejs.org/api/

Browser Name:

Chrome/Edge

Browser Version:

109.0.5414.120

Operation System:

Windows 11 Pro build 22621.1105

How to reproduce the issue:

Opening a page like https://nodejs.org/api/assert.html#trackercallsfn-exact scrolls to an incorrect position (different every time). Doesn't work in incognito mode either.
Works in firefox.

[ovflowd]

This happens because of some JavaScript code we own on the API page. (Not sure if this is related to that. But the link hashes are generated after the page load, and for all purposes, link hashes only work nicely when the initial DOM content contains it.

So it is possibly trying to scroll to the wrong area due to content-layout-shift. I can see this works nicely on the new API docs page

[ovflowd]

@Trott could we move this to nodejs/node as the API codebase is there?

[ovflowd]

@nodejs/issue-triage can we move this to node/node please?

[bmuenzenmeyer]

looking here as a member of the triage team, I do not have access to do so.

[ovflowd]

Oh, @bmuenzenmeyer is that because triage doesn't have access to this repository?

[tniessen]

@ovflowd Is this a duplicate of #40099?

[ovflowd]

Yes, it is related. It's mostly due to the fact that we don't render the non-visible sections of the page, but I think it is a Chromium bug to incorrectly calculate the distance. This happens due to the content-visibility CSS rule.

[ovflowd]

FWIW: On the new API docs we won't have an "all" page, or at least not a HTML one, since it's honestly unrealistic to render the entire API docs in one page and defeats the purpose of having dedicated files and navigation.

[ovflowd]

Duplicate of #40099