-
it took me to the posts just preceding comment11776451 rather than to that comment and those after it....
That might happen if, in the posts preceding the anchor point, images that have not yet loaded then load and move the page after the browser has already anchored.
There is no elegant fix for this.
In an ideal world I'd rewrite all IMG tags to include the height and width... but when images are third party, that is totally infeasible.
Velocio-
I dont think that this was the case here though, I know what you are describing - it taking you to one point, then images rendering and then moving - this was not it - images had rendered and I didn't get moved - see the images attached - 1st one is what it took me to, rather than the 2nd (which is what it now takes me to and what it should have taken me to originally)
It was just like it was pictured in the first attachement - with DJ's post being slightly cut off - as if it had anchored the post #544 just below the bottom of the page...
I will keep an eye out to see if I can spot it happen on pages that don't have any images on.
danb
@Velocio
I am now wondering about what I was seeing, as it doesn't seem to have happened again.
I do notice that when clicking on some links: https://www.lfgss.com/conversations/242376/?offset=525#comment11776451 for example, the anchor seems to be at the bottom of the page, rather than the top. i.e. it took me to the posts just preceding comment11776451 rather than to that comment and those after it....
edit When I then go and click on that link in this post it takes me to comment11776451 at the top of the page...
Other threads I click on (all from "today") seem to be anchoring at the top rather than bottom.