Re: [webkit-dev] Move to NavigationClient

2017-10-24 Thread Carlos Garcia Campos
El vie, 20-10-2017 a las 13:30 -0700, Alex Christensen escribió: > Right now we have an API::LoaderClient, API::PolicyClient and an > API::NavigationClient. We intend to remove the first two in the > future in favor of the API::NavigationClient. I have been working to > add calls to the

Re: [webkit-dev] Move to NavigationClient

2017-10-23 Thread Alex Christensen
I’m not sure I understand your concern. Deciding policies is definitely part of navigation. Why would it be important to have the clients be separate objects? > On Oct 22, 2017, at 9:22 AM, Alfonso Guerra wrote: > > > > On Oct 20, 2017 4:30 PM, "Alex Christensen"

Re: [webkit-dev] Move to NavigationClient

2017-10-22 Thread Alfonso Guerra
On Oct 20, 2017 4:30 PM, "Alex Christensen" wrote: Right now we have an API::LoaderClient, API::PolicyClient and an API::NavigationClient. We intend to remove the first two in the future in favor of the API::NavigationClient. Is there a semantic model this design

Re: [webkit-dev] Move to NavigationClient

2017-10-20 Thread Alex Christensen
Also, the authentication challenge API also needs redesigning. Right now you get an AuthenticationChallenge from which you get an AuthenticationDecisionListener to respond to. Could these become one object in the GTK API? The current design is based somewhat on the

Re: [webkit-dev] Move to NavigationClient

2017-10-20 Thread Michael Catanzaro
On Fri, Oct 20, 2017 at 3:30 PM, Alex Christensen wrote: Right now we have an API::LoaderClient, API::PolicyClient and an API::NavigationClient. We intend to remove the first two in the future in favor of the API::NavigationClient. I have been working to add calls to