Seems like the bug has been fixed upstream (on Firefox). Should we still leave the workaround here?