On Wed, May 29, 2019 at 2:53 PM Tomas Popela <tpopela@redhat.com> wrote:
it's this bug - https://bugs.chromium.org/p/chromium/issues/detail?id=949312 . It will probably be fixed in Chrome 76+ (current stable is Chrome 74), so that means it will take few months (unless someone from Chromium team backports it).

Yes, it's as I said - it's fixed in 76 - https://storage.googleapis.com/chromium-find-releases-static/114.html#11429f6b3ab962e68bc792e2af51c9858b383a76. I will mail some Chromium devs to consider backporting it.