Understood, thanks for the help
No problem. This is now fixed for the browser in my local build. Next patch rollout will resolve this issue - thanks for letting me know!
