"Posted At" seems to be occasionally hinky

January 25, 2005 10:05 AM

"Posted At" seems to be occasionally hinky. When I click the link to Mayor_Curley's embedded-image post (supposedly http://www.metafilter.com/mefi/38941#832736), it pops me to a different part of the page (http://www.metafilter.com/mefi/38941#832671) which is the first comment in the thread). I think I have seen that with some of my own posts in the past, perhaps when previewing, editing, previewing, editing, etc...
posted by mzurer to Bugs at 10:05 AM (14 comments total)

Works for me.

Occasionally the browser tries to jump to the anchor before the page has been fully loaded. Could that be a cause?
posted by DrJohnEvans at 10:35 AM on January 25, 2005

Are you using IE? It's appalling when it comes to #-anchors. Nothing you can do about it except use another browser, as far as I know.
posted by Pretty_Generic at 10:39 AM on January 25, 2005

I'm using Safari and OSX and I see the weird behavior that mzurer describes.
posted by jessamyn at 10:43 AM on January 25, 2005

WFM.
posted by monju_bosatsu at 11:17 AM on January 25, 2005

This problem doesn't vibrate for me using FireFox.
posted by DBAPaul at 11:17 AM on January 25, 2005

it's a browser thing. nuttin' to do with mefi. :-)
posted by quonsar at 11:17 AM on January 25, 2005

I am using konqueror and have had this problem for a long time. When I follow a link to a specific comment, it just jumps to the first comment of the thread. Using Mozilla or Firefox, and it works fine. Since Safari seems to have the same problem, this could just be a bug in the KHTML engine, but I don't know for sure. I know the last upgrade I did fixed what ever problem it was and now the anchors work like they are supposed to.
posted by chrisroberts at 11:18 AM on January 25, 2005

images that don't have specified heights screw up targeting in all sorts of browsers.

I believe a browser takes you to the right place immediately, then a 400px tall image loads and moves the page down.
posted by mathowie (staff) at 11:27 AM on January 25, 2005

I think Safari also has trouble finding anchors on longer pages. It's always been a problem here anyway.
posted by timeistight at 12:02 PM on January 25, 2005

'kay, so stupid question, but related:

How does one determine the permalink url for a specific comment?
posted by raedyn at 1:39 PM on January 25, 2005

raedyn: It's the "at [time]" link next to the name of the person commenting. In your case, it'd be 1:39 PM.
posted by abiku at 3:28 PM on January 25, 2005

I don't think the behaviour is exactly as you describe, Matt, but clearly it is browser-specific. Perhaps I ought to get my Moz' on.

A quick sampling of the page showed that clicking the other image-using post worked fine, and some of the others worked, some didn't.

If you like, I would be happy to do more debugging and report back...
posted by mzurer at 7:41 PM on January 25, 2005

Also - I am using Safari.
posted by mzurer at 7:41 PM on January 25, 2005

Much belated, but thank you abiku. New toy for raerae!
posted by raedyn at 8:21 AM on January 27, 2005