Documentation jump-to-header is buggy

[nicholaswmin]

Version

Chrome 125

Platform

Mac OS Sonoma

Subsystem

No response

What steps will reproduce the bug?

Visiting this: https://nodejs.org/api/test.html#running-tests-from-the-command-line

How often does it reproduce? Is there a required condition?

Always

What is the expected behavior? Why is that the expected behavior?

It jumps to the correct header

What do you see instead?

It jumps to the wrong header

Additional information

No response

[avivkeller]

Duplicate of #39776

[nicholaswmin]

Right - so the docs are broken for the past 3 years and the solution is to wait for a response from the Chromium team?

Want me to submit a PR?

[avivkeller]

If you’ve found a patch, feel free to suggest one :-)

[valadaptive]

As I mentioned in #39776, this is not a Chromium bug, and occurs in Firefox as well. I believe it was not previously showing up in Firefox simply because they had not yet implemented the relevant CSS feature.

It appears to be an effect of #37301. Lazy-loading the content means it is impossible for the browser to tell where to jump to, because it hasn't done the layout.

Optimizing for the case of reading the entire API docs on a single huge page, at the expense of making it frustrating and difficult to navigate the individual documentation sections that show up way more often in web search results, seems like the wrong decision to me.

[nicholaswmin]

@valadaptive indeed - well the idea I have is just a snipper of JS to scrollTo and offset.

But it's not gonna be accessible without JS. I'm on the fence on whether that's appropriate; @redyetidev

[avivkeller]

AFAIK the project doesn't have plans to use JS in the documentation.

But, the project is working on a redesign, which should patch this issue in the process. I wouldn't look to much into this issue, as when the redesign is done it'll (hopefully) be fixed.

[nicholaswmin]

Alright 👍

…

On Sat, 29 Jun 2024 at 4:48 PM, Aviv Keller ***@***.***> wrote: AFAIK the project doesn't have plans to use JS in the documentation. But, the project is working on a redesign, which should patch this issue in the process. I wouldn't look to much into this issue, as when the redesign is done it'll (hopefully) be fixed. — Reply to this email directly, view it on GitHub <#53584 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA56TPYY6ARRE77JNPINFQ3ZJ23J5AVCNFSM6AAAAABJ3X2Y6GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJYGIYDANJXGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>