Intended use case for granite.jquery's csrf.js
We’re running into some Javascript errors in Internet Explorer that we’ve tracked down to /etc/clientlibs/granite/jquery/granite/csrf/source/csrf.js
Specifically, the line handleForm(result.contentWindow.document)is a problem when an iframe contains content from a different domain.
I suspect I can set up an overlay to work around this, but wanted to get some input as far as what the intended use case for this behavior is, or if there are specific components in AEM that are relying on it, so we can be prepared for any future problems that may arise.
Thanks