Chrome Content API : dispatchDecidePolicyForNavigationAction equivalent

[nvineeth]

Hi All,
  I need the functionality of WebKit's FrameLoaderClient::dispatchDecidePolicyForNavigationAction. What is the equivalent API in Chrome content API?
Thanks.

[Charlie Reis]

RenderViewImpl::decidePolicyForNavigation is the the equivalent, but we don't have an arbitrary way to hook into that from a client of the content API.  The closest thing is ContentRendererClient::ShouldFork, which helps decide whether a process swap is needed or not.

Charlie

--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

[Avi Drissman]

On Thu, Sep 20, 2012 at 12:11 PM, Charlie Reis <cr...@chromium.org> wrote:

RenderViewImpl::decidePolicyForNavigation is the the equivalent, but we don't have an arbitrary way to hook into that from a client of the content API.

Note that the current Content API is based on what Chromium has needed from Content, and doesn't include many configuration points that would be reasonable to add.

If you can make a good case for adding a new API to Content, please do so!

Avi

[Darin Fisher]

Actually, you can use ResourceThrottle to somewhat mimic the functionality of dispatchDecidePolicyForNavigationAction.  A ResourceThrottle is given a ResourceController, which has the ability to Allow, Suspend, Cancel or CancelAndIgnore a network request.  (CancelAndIgnore is like WebCore::PolicyIgnore.)

The InterceptNavigationResourceThrottle is an example of using this interface to intercept certain navigations.

-Darin

--

[nvineeth]

Thank you all for the help. I am afraid InterceptNavigationResourceThrottle is not of much help, since the navigation type ( was the navigation initiated due link click, back, fwd, etc., ) is missing. If I can expose

RenderViewImpl::decidePolicyForNavigation at the content api, I will submit the patche.
Br,
nvineeth.

[Martin Kosiba]

The problem with adding decidePolicyForNavigation to the Content API is that you'd require synchronous IPC from the renderer to the browser, and that's discouraged. 

I think that the NavgationController::GetActiveEntry() would contain the info you're looking for, however the ActiveEntry is currently updated only after the provisional load is committed which is too late for your purposes. You could add a 'ProvisionalEntry' field to the NavigationController; it would be set in response to an async IPC sent from decidePolicyForNavigation (and would contain the info you're interested in), later you could retrieve that information in the ResourceThrottle and run your decision logic there.