Problem
inApp (inBrowser) messages interaction still works differently in Safari. No javascript results in no click tracking and no option for custom actions action://.... This restriction means it is basically restricted on all browsers when using a single campaign with custom actions.
Why is this still the case? Adding allow-scripts to the iframe sandbox attr, and removing the specific safari checks in the inApp code makes it work perfectly. What's the reason for not adding allow-scripts then? The content is controlled by iterable + us so where are the security concerns? Any other browser runs it anyway?
Problem
inApp (inBrowser) messages interaction still works differently in Safari. No javascript results in no click tracking and no option for custom actions
action://.... This restriction means it is basically restricted on all browsers when using a single campaign with custom actions.Why is this still the case? Adding
allow-scriptsto the iframe sandbox attr, and removing the specific safari checks in the inApp code makes it work perfectly. What's the reason for not addingallow-scriptsthen? The content is controlled by iterable + us so where are the security concerns? Any other browser runs it anyway?