On Thu, May 7, 2009 at 12:03 AM, Adam Barth <[email protected]> wrote: > On Wed, May 6, 2009 at 11:55 PM, Aaron Boodman <[email protected]> wrote: >> What about a setup where the content rendered in the tab area is >> running on chrome://, but contains a frame that hosts the actual feed >> running on http://foo.com? > > Sure, we could do that. Or even better is if the outer page is a > chrome-extension. Presumably we'll have a "subscribe to feed" API for > extensions?
On Thu, May 7, 2009 at 7:57 AM, Darin Fisher <[email protected]> wrote: > chrome:// pages cannot load HTTP-based sub-resources. We don't want to > taint the processes that render Chrome UI. Yeah, I actually meant chrome-extension:// for the outer page. But I don't know what to do about wanting the inner frame to have no authority. Hm. - a --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
