Ko tenda hembiapoite sa’ivéta oñemba’apokuévo hese hembiapo porãve hag̃ua. Peteĩ jehaipyre nomoĩporãiramo ne apañuái ha eporanduséramo, roguerekohína ore nepytyvõ rekoha ikatútava ndeykeko @FirefoxSupport Twitter-pe ha avei /r/firefox Reddit-pe.

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

When the adress contains #NameoOfASection, firefox looks it up too quickly

more options

E.g. when i open a Wikipedia page with a lot of latex content, the #NameoOfASection causes Firefox to find the right place for that exact second, way before the rest of the latex code has been sufficiently parsed/rendered for its final sizes to be found.

E.g. when i open a Wikipedia page with a lot of latex content, the #NameoOfASection causes Firefox to find the right place for that exact second, way before the rest of the latex code has been sufficiently parsed/rendered for its final sizes to be found.

Moambuepyre rousfv rupive

Opaite Mbohovái (1)

more options

Yes, I've seen that on this site, where some sidebar sections expand after the initial page load, pushing the content down the page from where the "hash" or "bookmark" or "anchor" was located. I'm not aware of any workarounds, although I'd love to know of one.

When I searched for bugs on file, I found one from 2011 about this, where it was characterized as a hard problem. When I think about it, suppose the page scrolls, how does Firefox know whether that is something is needs to correct for vs. something you caused to happen? Hmm...

Bug #668213 – External link to named anchor doesn't take you to anchor point on page

About the bug tracking system:

It sounds as though there is no imminent fix in the works (although sometimes fixing a seemingly unrelated Bug B will end up fixing Bug A).