Haven’t tested this under other browsers, but the anchor associated with every post on this board (<a href=“post66666”> for example) does not work if the post is the last one in a thread.
The last post in a thread also has an anchor of <a href=“newpost”> just below the <a href=“post66666”> anchor.
Could it be that netscape at least is getting confused? Maybe cause the two null links are right next to one another?
This is annoying cause I wanted to send a friend a link to an insightful metaphor employed by Gaudere.
Unfortunately, I’ll either have to link to newpost (which will be inaccurate if another post is made), or wait for someone to post something in the thread.
Here is the post I wanted to link to.
http://boards.straightdope.com/sdmb/showthread.php?threadid=40437&pagenumber=4#newpost
It is currently a correct link.
I need to reload Netscape (still picking up the pieces from the great computer crash of 10 days ago), but let me do that and see what happens. What version of Netscape are you currently using? Anybody else have a report on this issue?
your humble TubaDiva
Administrator
Here’s what I’ve found. At this moment the double anchor is on Jab1’s 10-20-00 9:48 am post on page 5.
The anchors are <a name=“post825566”></a> followed by <a name=“newpost”></a>.
Using the following link with Netscape 4.74 moves to the top of the page.
http://boards.straightdope.com/sdmb/showthread.php?threadid=40437&pagenumber=5#post825566
Using this link, you are moved to the proper post.
http://boards.straightdope.com/sdmb/showthread.php?threadid=40437&pagenumber=5#newpost
IE5 works almost the opposite way. The #post825566 link works properly and the #newpost portion of the second link is ignored as if there is no such anchor by that name and you aren’t repositioned within the page at all.
So, it seems to confuse both browers, but Netscape the most.
Jim
Netscape is working the same way, then. It is just that Netscape always goes to the top of the page when you reload a page. So presumably both are ignoring the anchor.
Could the two anchors be seperated in the code? Perhaps put one near say, the name of the poster, and the other near the beginning of the post?
That’s kinda what I was getting at. Both browsers ignore one of the 2 anchors. IE5 ignores the 2nd, Netscape ignores the 1st. IE5 doesn’t change position on the page for a non-existent anchor and Netscape moves to the top of the page on a non-existent.
The bigger problem is why there is a “newpost” anchor there in the first place. In the examble I used above, there were 2 more post following the one in question.
Jim