@lapetiteboite,

What version of safari are you using? this is what we see. Could this be a cache issue on the server or browser?