• it's because the page loads at the correct place before the pictures are taken into account.

    Never had this issue with Chrome though. Firefox's fault?

About