Comment by codigrade

Hello, thank you for pointing it out. Sadly, it's an old bug of Safari. Refreshing your cache should make it work