I might have indicated it's DOMPurify's problem. Sorry I didn't mean that. The browser add-on is unfortunately not open source and I don't want to spend a lot

I might have indicated it's DOMPurify's problem. Sorry I didn't mean that. The browser add-on is unfortunately not open source and I don't want to spend a lot of time to investigate it. According an earlier issue (#1437), they should have fixed it already. I guess the later envolvements changed that. I agree with you that what DOMPurify does should be cared of by the Browser.