by HB on Thu Apr 19, 2007 2:38 pm
Really? It works for me.
Maybe it's the browser not scrolling correctly? Images within a thread can throw off the browser's handling of HTML anchors (the # that follows the URL). This happens because the images are loaded separately and the <img> tags don't include the height because it's not known, so the browser can't calculate precisely where to scroll to bring the anchor to the top. It guesses -- usually wrongly -- and thus the browser doesn't scroll far enough. It's a tradeoff between allowing different image sizes and look ahead fidelity. Some sites avoid this problem by resizing all images to the same height so the <img> tag accurately reflects the size the image will be when it's finally loaded.
BTW, if a thread had lots of images to load and they're large, waiting a few seconds for them to load and then pressing Enter on the URL will properly rescroll to the precise location of the HTML anchor. It's ugly, but I don't have an easier solution. The options are (a) fixing the size of images, or (b) recording their sizes in the database when they're uploaded, which costs in performance and can "break" for offsite images that are later resized. Neither is a perfect answer.
Dan Kehn