Looks like I’ve found a workaround, if I host the page in s3 and embed that into a html element using an frame it seems to avoid the issue