Skip to main content
Information Security

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • 1
    I'm having trouble understanding the problem. It sounds like it's all client-side code (javascript)? What are the third party "views" for if they are in invisible iframes? Is it to enrich data presented elsewhere on the page? Then why not do this on the server side where you'll have much more control? Commented May 19, 2012 at 9:50
  • I agree with @LouisSomers, I don't get what you want to do exactly. In what will be made the view? Do you mean the third party will be able to have their own view (HTML/JS/CSS) in your website? Commented May 19, 2012 at 14:30
  • The goal is a bit similar to what Google Wave did: provide a "generic" data model, persistence, communication, etc, while allowing third parties to build new things upon it. In principle the iframes were not meant to be invisible (so yes, they would provide HTML/JS/CSS) but I'm more inclined toward restricting extensions to the role of "controller" (which will render the view solely through my API). The problem I'm trying to solve is determine the viability of all this, and it boils down to the question: are there unforeseen consequences of having untrusted third party code running in iframes? Commented May 19, 2012 at 18:35