BTW I think this API (and the associated registerContentHandler) aren't that great... imagine a feed reader that wants to handle feed types and feed protocol links... do they need to call these functions one per protocol scheme and per feed content type (there are several), showing a UI for each? This sort of thing seems better handled through some kind of manifest.
-Ben On Thu, Oct 1, 2009 at 8:06 PM, Darin Fisher <[email protected]> wrote: > I've added this to my list for review by the group. > -Darin > > On Thu, Oct 1, 2009 at 1:36 PM, Brian Rakowski <[email protected]> wrote: >> >> You should talk with the open web leads (darin, ifette, dglazkov, >> slightlyoff) for help on floating this out there. >> >> On Thu, Oct 1, 2009 at 1:12 PM, Nick Baum <[email protected]> wrote: >>> >>> I've never done this, but I'm happy to learn. I got an intro to how to do >>> it a few weeks back re:some extensions APIs. >>> Where do I send the email? I'll send out a draft here beforehand. >>> >>> -Nick >>> >>> On Thu, Oct 1, 2009 at 2:41 PM, Brad Green (大面包) <[email protected]> wrote: >>>> >>>> >> >>>> >> > API: How does the page know it's registered? >>>> >> >>>> > If Gmail notices you have Chrome and this isn't set, it might put a >>>> > big >>>> > promo on your inbox page. However, if it's already set, if would of >>>> > course >>>> > want to hide this. >>>> >>>> I understand your point now. It is something that should be brought >>>> up in whatwg and discussed. >>> >> >> >> >> > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
