It should be safe to remove this workaround, as we are officially
supporting the last three major versions of Chrome, so at time of this
writing Chrom >= 86. Furthermore they even fixed it in a patch release
for Chrome 84, namely 84.0.4147.125.