BTW this is present as late as Chrome Canary 82. So it looks like it's here to stay? Ugh, submitting a bug to Chromium for this is gonna be rough.
Oh wow, well at least it's been caught now and hopefully the solution you've found works for everyone going forward. I'll keep an eye on the blog posts and any other updates which come from it.