Re: Status of web intents in Chrome

Thanks for the question. I've heard from several people wondering the same
thing. :-)

Our status in Chrome-land is we're waiting for inspiration to strike with
respect to the UI issues I talked about at TPAC. It is true that James and
I are also busy with other work, but the obstacle isn't that so much as
being unsatisfied with the experimental implementation we did. We've been
waiting to put more work into the spec or implementation until we get some
of those issues ironed out. I hope that what Mounir learns from the Firefox
OS deployment will also be really important to include as we think more
about what we want it to look like. So the upshot is that we're currently
in a holding pattern, and the experimental implementation is disabled by
default in the shipping browser.



On Thu, Jan 17, 2013 at 11:55 PM, Jungkee Song <jungkee.song@samsung.com>wrote:

> Hi Greg, Mounir,
>
> Do you have any updates what's going on after the discussion we had in
> Lyon?
>
> Regards,
> Jungkee
>
>
> > -----Original Message-----
> > From: Greg Billock [mailto:gbillock@google.com]
> > Sent: Friday, November 02, 2012 3:47 AM
> > To: WebIntents
> > Subject: Status of web intents in Chrome
> >
> > We shipped experimental support for web intents in Chrome in order to
> > gather data and feedback about the API and help inform its
> > development. Now that we've gathered enough data, we've disabled the
> > experimental support for web intents as of version 24. After carefully
> > reviewing the feature, we have identified a number of areas for
> > development in both the API and specific user experience in Chrome.
> > We'll use the results of this experiment to help us make sure we're
> > approaching the important problem of inter-webapp communication in the
> > best possible way. As we review the results, we'll endeavor to share
> > our findings more widely. We're still interested in this problem space
> > and will continue to explore it.
> >
> > --Greg Billock
>
>