It looks like a new issue in recent versions of Chrome and Edge, and I have found a similar report in Chromium Issues. You can report your issue there and see the next steps by Chromium Dev Team.