An active bug from 12/12/2018 that Google and the Chromium team just dont want to fix for 'reasons'.

First time I stumbled over this bug myself I thought that will be fixed soon. When Microsoft started using Chromium I thought "for sure now they will".

Turns out there is something nefarious going on. There is no other explanation.

In my experience, bugs like this (priority - medium, severity - unrated) only fix in case if they don't require a lot of time to fix.