We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

mid-page links do not work reliably in Firefox

  • 1 reply
  • 1 has this problem
  • 1 view
  • Last reply by cor-el

DB
DB
more options

If you click on a mid-page link such as: https://jitsi.org/Documentation/FAQ#passwd-rst

Firefox does not always jump to the "password-rst" section. Often it will load at the top of the page and ignore the mid-page anchor.

My current workaround in these situations is to wait for Firefox to finish loading the page then click on the location bar and hit Enter to jump to the mid-page anchor.

Maybe Firefox has some race conditions bug?

If you click on a mid-page link such as: https://jitsi.org/Documentation/FAQ#passwd-rst Firefox does not always jump to the "password-rst" section. Often it will load at the top of the page and ignore the mid-page anchor. My current workaround in these situations is to wait for Firefox to finish loading the page then click on the location bar and hit Enter to jump to the mid-page anchor. Maybe Firefox has some race conditions bug?

All Replies (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

It is possible the Firefox isn't able to determine the exact position of an anchor during the loading page as there may still be images and other content that hasn't arrived yet.
Sometimes there are also scripts that modify the page after the loading has finished.

Also if you try to scroll the page before the loading has finished then it can go wrong.

The code on the page that you posted doesn't look that complicated although there are script running and it works for me.

Such issues can be caused by an extension that isn't working properly.