I think your fix is the fix though - as the screenshots I received (thanks @adalia-bipunctata) showing the issue were taken a few minutes after. That isn't proof, but would indicate you did resolve this by clearing browser cache.
Thanks @gedwin for clearing his cache - this lead to spotting a file that had changed (1 single character!) that had most likely been cached from the previous version. This is now being forced to reload to refresh it, as it should have been all along.
So, everyone should be fine now without clearing their cache. Thanks all for helping to troubleshoot this.
@russsaid Thanks @gedwin for clearing his cache - this lead to spotting a file that had changed (1 single character!) that had most likely been cached from the previous version. This is now being forced to reload to refresh it, as it should have been all along.
So, everyone should be fine now without clearing their cache. Thanks all for helping to troubleshoot this.
@russsaid Thanks @gedwin for clearing his cache - this lead to spotting a file that had changed (1 single character!) that had most likely been cached from the previous version. This is now being forced to reload to refresh it, as it should have been all along.
Ah, the evil bit syndrome. Tiny cause, big effect.