(We talked about a spreadsheet for this... anyone have a link?)
I'm following the chain from "<rtn> on URL in browser" --> "tell renderer do
something". This currently ends at tabs; I'm removing stubs (TabContents,
TabContentsDelegate, ...) and bringing in the real thing.
jrg
On Mon, Feb 9, 2009 at 1:12 PM, Thomas Van Lenten <thoma...@chromium.org>wrote:
> Follow up from the other week -
>
> I'm still digging into ProcessUtil::LaunchApp and the fall out from there.
> The current code in unittests and w/in chromium depends on a few things that
> windows offers since it gets handlers for this, the Mac & Linux world can't
> really map things like this, so we're going to end up needed a slightly
> beefer process object to provide some of what is needed (hopefully we'll be
> able to leave the unittests on the current api for now, the problems doesn't
> really cause the tests issues (or we've fixed them)).
>
> TVL
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
