What 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.