@Wakey,
Thanks for reaching out to us. The issue you’re encountering is actually already known and has been logged on our GitHub page for our team to review here:
Apologies for any inconvenience this may cause you. You’ll likely see this issue addressed in a future update to the browser. I’ve added your report to the thread as well on your behalf.
1 Like