On Monday, March 25, 2013 9:57:20 PM UTC+1, [email protected] wrote: > Hi, > > > > Our web application is a composite one where external apps can be injected in > the main content flow. For example a reading activity can embed an > assignment. We are naturally using IFrames for that. As the apps that are > embedded are usually complex pre-existing apps, they are more often than not > relying on session cookies and are originating from another domain. > > > > We have kind of ignored the Mac/Safari issue up until now, but with this > move, we must be more pro-active as the size of the potentially impacted > population is much bigger (and from what I get things that were working will > stop suddenly to work when the FF update is pushed). > > > > So what I am after is the recommended approach: should the embedded app > recognize the cookie set was not honored and fire up a pop-up so set in a > main window? Is that the recommended approach? Or is there a less intrusive > (I’ve read DOM actions in the IFrame) that could be taken? > > > > Any guideline on how our embedded apps could be made ready would be > appreciated! > > > > Thanks, > > > > Claude
Hi Claude, I am more or less in the same situation (actually, more more than less). Did you get make any progress in your research or dis you get any insights from your original post ? Many thanks ! Stephane _______________________________________________ dev-privacy mailing list [email protected] https://lists.mozilla.org/listinfo/dev-privacy
