Fortunately, according to a patch spotted by one X (Twitter) user, a Microsoft engineer has found a solution to the issue, so you can expect the problem to be history once Chrome and Edge are next ...