Hello!
I just looked and it seems to be fixed for me:
It also appears that it was taken note of in the release from Tuesday:
