Comment 4 for bug 2063049

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Looks like the fix is in Chrome 124.0.6367.118