JMP Save As Dynamic HTML - make sure it works in cross-site IFRAMESWhat inspired this wish list request?
The JMP dynamic HTML in JMP 17 broke with our internal solution where dynamic HTML reports are saved on one department's website, but IFRAME embedded in another department's site (different server URL). The specific problem is that JMP 17's HTML javascript used 'window.parent.document', which makes the document in the IFRAME attempt to access the document in the parent window - which is a violation of browser/javascript cross-site scripting policies.
What is the improvement you would like to see?
There is no reason why JMP HTML documents cannot be stand-alone, and no reason why they need to access the parent window to an IFRAME. Please make sure that no JMP dynamic HTML javascript attempts to violate or cross the HTML parent/child window document boundary.
Why is this idea important?
Because it allows collaborative HTML document sharing.
Content OrganizationSharing and Communicating ResultsRe: JMP Save As Dynamic HTML - make sure it works in cross-site IFRAMES - Status changed to: AcknowledgedRe: JMP Save As Dynamic HTML - make sure it works in cross-site IFRAMES - Status changed to: Yes, Stay Tuned!We are planning on including this in a future release of JMP.
Re: JMP Save As Dynamic HTML - make sure it works in cross-site IFRAMES@dieter_pisot @mia_stephens this was most likely fixed in JMP18?
Re: JMP Save As Dynamic HTML - make sure it works in cross-site IFRAMES@jthi this wish has been delivered in 18. please let us know if it does not fulfill your request and we can re-open this request and review any feedback you have
Re: JMP Save As Dynamic HTML - make sure it works in cross-site IFRAMESI was mostly wondering why the state of this wish list item is "Yes, Stay Tuned!" and not "Delivered"?
Re: JMP Save As Dynamic HTML - make sure it works in cross-site IFRAMES - Status changed to: DeliveredThanks @jthi , changed to Delivered.
