Hi iantonge,

I just tested this to see what happens in my local app with a strict CSP set. When using the swap='morph:xxxxx' swap format it does indeed throw unsafe eval CSP warnings. But if your application only uses the safe non eval versions then you should not get any CSP violation warnings which I think this is really equivalent to the safe.js version you were thinking about anyway. htmx has a nicer option to disables its use of eval so you never get the warnings and the eval functions just fail silently but I think getting the warnings while your developing and testing your app is quite a good thing as long as you know to check your console for issues.

Also a note that most of the advanced idiomorph behavior options that you can set via the eval can also be set via javascript updating Idiomorph.defaults object to override the defaults.

Thanks for taking the time to look at this. My experience was that I got a CSP violation and the js fell over even though that line was never hit - although testing it in a fresh project now I can see that is not the case. I can only assume I had a typo which meant that actually that line was hit. I think we can chalk this up to "Problem exists between keyboard and chair".