That was just an example script to explain the issue.

All our custom events are written in jQuery. Migration is getting tough for us.

I am not using the experience cloud id service. I am just loading it a java script via rules as that is how it was done in signal previously. The actual issue is:For example if the javascript is as below.<script>    var test = '<script src=""><\script>';    var test1="adasd";</script>Browser will tr...

Thank you so much for your help and registering the case with window object

I am trying to load Adobe Visitor API for JavaScript version: 1.7.0 via Adobe Launch rule but the code is coming out of script tag after certain code.<script>somecode</script>remaining code coming out of script tagNot sure why its happening.any better way to load libraries ??

For now I have done as below. I will keep on adding all events as I find.$(window).on('event1 event2 event3',function(e) {  document.body.dispatchEvent(new CustomEvent(e.type));});

Yeah I can do that but i am not sure how many custom events we have.

window custom events are not working on LAUNCH

window doesn't work We are migrating from SIGNAL to LAUNCH. custom window events work fine there but it is not working here.

There is a lot of code written with window trigger in analytics. It would be tough to modify all.It works fine with body custom events. Also jquery way of triggering custom event is not working