Good news, this is now been fixed in Edge Canary. This means that the next time Edge Dev updates itself, this will be resolved there too. Edge Dev is updated weekly I think, so it should be a matter of a few days.
Good news, this is now been fixed in Edge Canary. This means that the next time Edge Dev updates itself, this will be resolved there too. Edge Dev is updated weekly I think, so it should be a matter of a few days.