My suspicion is that if you do find a way around it, you can expect it to be blocked again in a following update. Security changes are rarely reversed.
Thanks, Shane, not what I wanted to hear. Unfortunately, it’s what I expected to hear.
If I build this as a Cocoa AppleScript app and use webkit, I should be able to capture user input without cross-source conflict. Yes? I’ve been writing AppleScript for many years and AppleScriptObjC since Yosemite, but I’m a Cocoa newbie.
If you mean it will give you a way around it – I very much doubt it.
No, sorry, I guess I wasn’t clear. What I meant was to display the HTML within the Cocoa-AppleScript app using webkit and capture the user’s actions so the post is not necessary. Hence no cross-source issue.
You can certainly display the HTML.