You are reading a single comment by @danb and its replies.
Click here to read the full conversation.
-
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.
2 Attachments
-
danb
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.