<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:dtvmedia="http://participatoryculture.org/RSSModules/dtv/1.0"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Cross-Domain Communication with IFrames</title>
	<atom:link href="http://softwareas.com/cross-domain-communication-with-iframes/feed" rel="self" type="application/rss+xml" />
	<link>http://softwareas.com/cross-domain-communication-with-iframes</link>
	<description>Mahemoff's Podcast/Blog - Web, Programming, Usability from the Author of 'Ajax Design Patterns' (AjaxPatterns.org)</description>
	<lastBuildDate>Tue, 16 Mar 2010 19:17:45 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.3</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: technofreak</title>
		<link>http://softwareas.com/cross-domain-communication-with-iframes/comment-page-2#comment-469851</link>
		<dc:creator>technofreak</dc:creator>
		<pubDate>Mon, 15 Mar 2010 08:42:17 +0000</pubDate>
		<guid isPermaLink="false">http://softwareas.com/cross-domain-communication-with-iframes#comment-469851</guid>
		<description>&lt;p&gt;can iframe be left in comment?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>can iframe be left in comment?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zak</title>
		<link>http://softwareas.com/cross-domain-communication-with-iframes/comment-page-2#comment-468806</link>
		<dc:creator>Zak</dc:creator>
		<pubDate>Sun, 07 Mar 2010 07:24:19 +0000</pubDate>
		<guid isPermaLink="false">http://softwareas.com/cross-domain-communication-with-iframes#comment-468806</guid>
		<description>&lt;p&gt;Fantastic article. Loved how the hacks were presented in an &quot;evolutionary&quot; manner. Thank you!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Fantastic article. Loved how the hacks were presented in an &#8220;evolutionary&#8221; manner. Thank you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: george</title>
		<link>http://softwareas.com/cross-domain-communication-with-iframes/comment-page-2#comment-468088</link>
		<dc:creator>george</dc:creator>
		<pubDate>Mon, 01 Mar 2010 17:43:47 +0000</pubDate>
		<guid isPermaLink="false">http://softwareas.com/cross-domain-communication-with-iframes#comment-468088</guid>
		<description>&lt;p&gt;Your well written article provides a solid conceptual foundation rarely found in the world of cyberhelp as well as &quot;hope&quot; for the future.  Thanks!&lt;/p&gt;

&lt;p&gt;I do have one question pertaining to a specific situation. &lt;/p&gt;

&lt;p&gt;I have a project in the works, which ultimately would be a fb app, but for now is still in my java editor.&lt;/p&gt;

&lt;p&gt;It has among others things a fb iframe primarily so that I can see what i am styling.  When I am finished, I will flip it around so that the fb page is the main page and everything else is in a iframe.&lt;/p&gt;

&lt;p&gt;Everything was fine for a week or ten days, then a day or two ago, I noticed that the equivalent of a &quot;opacity screen&quot; (dark gray about 15%) was over the iframe in question after log-in to the that iframe.&lt;/p&gt;

&lt;p&gt;I have over 1000 lines of code and no reference to layer, opacity, filter, focus or anything remotely connected to the problem at hand.&lt;/p&gt;

&lt;p&gt;Could it be that it originates in the source?&lt;/p&gt;

&lt;p&gt;Somehow, I am thinking that your article answers this question in a general way, but I am looking for a more specific answer.&lt;/p&gt;

&lt;p&gt;Thank in advance you for your prompt reply.&lt;/p&gt;

&lt;p&gt;In the meantime, I going to go see if you have written anymore articles of similar quality.&lt;/p&gt;

&lt;p&gt;Best Regards,
g&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Your well written article provides a solid conceptual foundation rarely found in the world of cyberhelp as well as &#8220;hope&#8221; for the future.  Thanks!</p>
<p>I do have one question pertaining to a specific situation. </p>
<p>I have a project in the works, which ultimately would be a fb app, but for now is still in my java editor.</p>
<p>It has among others things a fb iframe primarily so that I can see what i am styling.  When I am finished, I will flip it around so that the fb page is the main page and everything else is in a iframe.</p>
<p>Everything was fine for a week or ten days, then a day or two ago, I noticed that the equivalent of a &#8220;opacity screen&#8221; (dark gray about 15%) was over the iframe in question after log-in to the that iframe.</p>
<p>I have over 1000 lines of code and no reference to layer, opacity, filter, focus or anything remotely connected to the problem at hand.</p>
<p>Could it be that it originates in the source?</p>
<p>Somehow, I am thinking that your article answers this question in a general way, but I am looking for a more specific answer.</p>
<p>Thank in advance you for your prompt reply.</p>
<p>In the meantime, I going to go see if you have written anymore articles of similar quality.</p>
<p>Best Regards,<br />
g</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ygl</title>
		<link>http://softwareas.com/cross-domain-communication-with-iframes/comment-page-2#comment-467635</link>
		<dc:creator>ygl</dc:creator>
		<pubDate>Thu, 25 Feb 2010 00:28:04 +0000</pubDate>
		<guid isPermaLink="false">http://softwareas.com/cross-domain-communication-with-iframes#comment-467635</guid>
		<description>&lt;p&gt;Here is a short description of cross-domain with iframes.
http://egladysh.blogspot.com/2010/02/cross-domain-request-pattern.html&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Here is a short description of cross-domain with iframes.<br />
<a href="http://egladysh.blogspot.com/2010/02/cross-domain-request-pattern.html" rel="nofollow">http://egladysh.blogspot.com/2010/02/cross-domain-request-pattern.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blake</title>
		<link>http://softwareas.com/cross-domain-communication-with-iframes/comment-page-2#comment-467632</link>
		<dc:creator>Blake</dc:creator>
		<pubDate>Thu, 25 Feb 2010 00:10:19 +0000</pubDate>
		<guid isPermaLink="false">http://softwareas.com/cross-domain-communication-with-iframes#comment-467632</guid>
		<description>&lt;p&gt;Great article.  I&#039;ve been working with OpenSocial and Facebook for awhile, and while they support cross-domain iframes, it&#039;s always been unclear as to what exactly is going on.  Thanks for the explanations.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Great article.  I&#8217;ve been working with OpenSocial and Facebook for awhile, and while they support cross-domain iframes, it&#8217;s always been unclear as to what exactly is going on.  Thanks for the explanations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Unintended Consequences and the Inevitable &#8220;Why Would Anyone Want To Do This?&#8221;</title>
		<link>http://softwareas.com/cross-domain-communication-with-iframes/comment-page-2#comment-466879</link>
		<dc:creator>Unintended Consequences and the Inevitable &#8220;Why Would Anyone Want To Do This?&#8221;</dc:creator>
		<pubDate>Tue, 16 Feb 2010 20:53:17 +0000</pubDate>
		<guid isPermaLink="false">http://softwareas.com/cross-domain-communication-with-iframes#comment-466879</guid>
		<description>&lt;p&gt;[...] been willing to fool around with the not-so-always-obvious features of web browsers. Take cross-domain iframe messaging, for example. Not something people knew much about until a few years ago, when James Burke [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] been willing to fool around with the not-so-always-obvious features of web browsers. Take cross-domain iframe messaging, for example. Not something people knew much about until a few years ago, when James Burke [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vinay</title>
		<link>http://softwareas.com/cross-domain-communication-with-iframes/comment-page-2#comment-465655</link>
		<dc:creator>vinay</dc:creator>
		<pubDate>Tue, 02 Feb 2010 12:53:10 +0000</pubDate>
		<guid isPermaLink="false">http://softwareas.com/cross-domain-communication-with-iframes#comment-465655</guid>
		<description>&lt;p&gt;I am sick of this cross domain issue. duhhh... i have a page which has 2 iframes , but the href of both the iframes are in different domain. what i need to set a hash from one iframe to the other. i tried all the methods you guyz posted above but none of these are working. could you please help me on this.?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I am sick of this cross domain issue. duhhh&#8230; i have a page which has 2 iframes , but the href of both the iframes are in different domain. what i need to set a hash from one iframe to the other. i tried all the methods you guyz posted above but none of these are working. could you please help me on this.?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2009-12-11 &#171; Caiwangqin&#8217;s delicious bog</title>
		<link>http://softwareas.com/cross-domain-communication-with-iframes/comment-page-2#comment-461343</link>
		<dc:creator>links for 2009-12-11 &#171; Caiwangqin&#8217;s delicious bog</dc:creator>
		<pubDate>Fri, 11 Dec 2009 23:09:14 +0000</pubDate>
		<guid isPermaLink="false">http://softwareas.com/cross-domain-communication-with-iframes#comment-461343</guid>
		<description>&lt;p&gt;[...] Cross-Domain Communication with IFrames (tags: iframe xhr cross-domain ajax web browser) [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] Cross-Domain Communication with IFrames (tags: iframe xhr cross-domain ajax web browser) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh Scribner</title>
		<link>http://softwareas.com/cross-domain-communication-with-iframes/comment-page-2#comment-460587</link>
		<dc:creator>Josh Scribner</dc:creator>
		<pubDate>Fri, 04 Dec 2009 16:38:10 +0000</pubDate>
		<guid isPermaLink="false">http://softwareas.com/cross-domain-communication-with-iframes#comment-460587</guid>
		<description>&lt;p&gt;&lt;/p&gt;
</description>
		<content:encoded><![CDATA[</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh Scribner</title>
		<link>http://softwareas.com/cross-domain-communication-with-iframes/comment-page-1#comment-460586</link>
		<dc:creator>Josh Scribner</dc:creator>
		<pubDate>Fri, 04 Dec 2009 16:36:00 +0000</pubDate>
		<guid isPermaLink="false">http://softwareas.com/cross-domain-communication-with-iframes#comment-460586</guid>
		<description>&lt;p&gt;We&#039;ve been wrestling with this problem too.  We have an application (A, domain a.xyz.com) which would like to display only a small portion of the data created by a legacy app (B domain b.xyz.com).  B exposes its data via HTML, and can easily be placed in an iframe, but the results are ugly.&lt;/p&gt;

&lt;p&gt;We attempted to make peace using Law II, using javascript we would tell both pages they were the same domain:&lt;/p&gt;

&lt;p&gt;The developers of B were willing to place a small piece of  code on their page, so long as they didn&#039;t have to tangle with the data.  We asked for the script document.domain=xyz.com
Then, on A, we did the same.&lt;/p&gt;

&lt;p&gt;&lt;/p&gt;

&lt;p&gt;I&#039;m not sure if you have any insight on this, but I&#039;m posting it in the hopes it will help others (you are not alone).  Meanwhile, I&#039;m off to try other approaches.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>We&#8217;ve been wrestling with this problem too.  We have an application (A, domain a.xyz.com) which would like to display only a small portion of the data created by a legacy app (B domain b.xyz.com).  B exposes its data via HTML, and can easily be placed in an iframe, but the results are ugly.</p>
<p>We attempted to make peace using Law II, using javascript we would tell both pages they were the same domain:</p>
<p>The developers of B were willing to place a small piece of  code on their page, so long as they didn&#8217;t have to tangle with the data.  We asked for the script document.domain=xyz.com<br />
Then, on A, we did the same.</p>
</p>
<p>I&#8217;m not sure if you have any insight on this, but I&#8217;m posting it in the hopes it will help others (you are not alone).  Meanwhile, I&#8217;m off to try other approaches.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
