The cause of the problem is related to EXTERNAL .CSS DOCUMENTS.
For whatever reason, when Safari is prompted to load the external css, it “pauses” the process of displaying the page until the css document has finished classifying how things are supposed to look.
Safari does not, however, cease it’s attempt to load the anchor target on the page.
So, while css is holding the page layout in it’s grasp, Safari aims to find something which doesn’t yet exist. Hence, nothing happens (but the page sure ends up looking pretty).
More info can be found here:
There is a lot of analysis in this bug report, but I am not sure if it is accurate. That was not written by me, but by the person who reported the radar. I have not done any investigation on this so I can neither confirm nor deny that that is the cause.
This is the URL: http://lastexit.thecivilpartnership.com/article/at-the-arcades#c000003
It seems to work without fail in Safari 2.0. I have found that it sometimes works in TOT, and sometimes does not. It seems to be more likely to fail if it tries to load the page on launch.
I believe this was fixed with r24550.
*** Bug 9549 has been marked as a duplicate of this bug. ***
Probably a duplicate of Bug 3390 as well.
*** This bug has been marked as a duplicate of 3390 ***