Hi @Luke Vo,
Thank you for the code. I can successfully reproduce this problem on every channel of Microsoft Edge, but not on Chrome. To me it seems to be a problem that is unknown to Dev Team since higher versions of Edge still has this problem. You can stick to the quick fix first, and submit feedback here to make Dev Team aware of this issue. Hopefully they will bring the change to the next releases.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Best Regards,
Shijie Li