It's the twitter embeds and the way twitter provides the functionality to 'render' a tweet.
When someone posts a tweet, the post content is just the tweet number, so the page loads with that. Then after that twitter's Javascript code goes through and replaces all the HTML containing the tweet number with the full code to display the tweet.
The page jump happens before this so it puts you at the right place, but then the tweets get put in which are longer, so it pushes the bottom of the page further down.
It's annoying I agree, but I can't really think of a good way to deal with it.
__________________
Uncertainty is an uncomfortable position.
But certainty is an absurd one.
|