Actually, after digging a bit, it appears that we had an open issue to fix this and a fix has already been pushed:
I’ve pinged the devs about uplifting the fix to the next browser update – if that does not go through, the fix will work its way through the release pipeline until it hits stable.