- From: John J Barton <johnjbarton@johnjbarton.com>
- Date: Mon, 20 Feb 2012 09:22:56 -0800
- To: Paul Kinlan <paulkinlan@google.com>
- Cc: Rachel Blum <groby@google.com>, Greg Billock <gbillock@google.com>, public-web-intents@w3.org
Oh, sorry. I ended up here after I asked on public-webapps about a standard way to establish communications between cross-domain iframes and a web page. Allowing plugin authors and plugin users to succeed without negotiating with the framework authors is powerful advantage. The use case, plugins for development tools, closely resembles web-intents. The plugin API could be as simple as image exchange like the memegen example (hence my interest in web-intents) or more complicated exchanges requiring two way operations (hence my questions about using postMessage). But iframes cannot participate in web-intents so we are out of luck. jjb On Mon, Feb 20, 2012 at 8:58 AM, Paul Kinlan <paulkinlan@google.com> wrote: > why? > > > On Mon, Feb 20, 2012 at 4:38 PM, John J Barton <johnjbarton@johnjbarton.com> > wrote: >> >> Ok, thanks for the info. Sounds like we will have to look elsewhere >> for a cross-domain application integration framework. >> jjb >> >> On Mon, Feb 20, 2012 at 5:02 AM, Paul Kinlan <paulkinlan@google.com> >> wrote: >> > No. The shim blocks all registrations from occurring inside an iframe. >> > I >> > would expect the native implementation to do the same. If the spec >> > doesn't >> > mention this, it should. >> > >> > On Fri, Feb 17, 2012 at 11:55 PM, John J Barton >> > <johnjbarton@johnjbarton.com> wrote: >> >> >> >> On Fri, Feb 17, 2012 at 3:41 PM, Rachel Blum <groby@google.com> wrote: >> >> > >> >> >> >> >> >> > Why wouldn't I race James to create WorldsMostAwesomeWebIntents >> >> >> > page >> >> >> > full of <intent> tags? >> >> >> > Won't people be motivated to create ad supported lists? Won't >> >> >> > users >> >> >> > be >> >> >> > bombarded with <intent> pages? >> >> >> > I guess these are problems you'd love to have. >> >> > >> >> > >> >> > Let's keep in mind that (unless I misremember) intent tags have a >> >> > same-origin restriction on the action path. >> >> > >> >> > So you'll actually need to do a bit of work beyond just collecting >> >> > tags >> >> > on >> >> > your page - unless you choose to provide no-op intents. >> >> >> >> I guess a page full of >> >> <iframe src=<page-with-intent-tag>> >> >> wouid work, right? >> >> >> >> jjb >> >> >> >> >> >> > >> >> > Rachel >> >> >> > >> > >> > >> > -- >> > Paul Kinlan >> > Developer Advocate @ Google for Chrome and HTML5 >> > G+: http://plus.ly/paul.kinlan >> > t: +447730517944 >> > tw: @Paul_Kinlan >> > LinkedIn: http://uk.linkedin.com/in/paulkinlan >> > Blog: http://paul.kinlan.me >> > Skype: paul.kinlan >> > > > > > > -- > Paul Kinlan > Developer Advocate @ Google for Chrome and HTML5 > G+: http://plus.ly/paul.kinlan > t: +447730517944 > tw: @Paul_Kinlan > LinkedIn: http://uk.linkedin.com/in/paulkinlan > Blog: http://paul.kinlan.me > Skype: paul.kinlan >
Received on Monday, 20 February 2012 17:23:27 UTC