[webkit-qt] decidePolicyForNavigationAction QML API

[simon.hausmann at nokia.com]

Apologies for the gorgeous top-quote :/

1) In terms of ownership we could either go for JS ownership and delete the QObject when we're done. Or we just make it a child of the view and also delete when we're done.

2) I think the engine can handle loads inbetween. But yeah, that's worth an audit.


Simon

________________________________________
From: ext Caio Marcelo de Oliveira Filho [caio.oliveira at openbossa.org]
Sent: Thursday, October 13, 2011 19:13
To: Hausmann Simon (Nokia-MP-Qt/Oslo)
Cc: webkit-qt at lists.webkit.org
Subject: Re: [webkit-qt] decidePolicyForNavigationAction QML API

Hello,

> The WebView component gets a signal navigationRequested (naturally the name is just a proposal) that provides a "NavigationRequest" object (that internally wraps a WKFramePolicyListenerRef) and which provides corresponding methods/slots for use/download/ignore. This changes the usage to the following pattern:

+1

I'm the author of the current implementation and I think this will be
a real improvement.

Couple of questions: who will delete the request objects (maybe
themselves when answer function called...)?
And do we expect to webView be in a "consistent" state in the meantime
-- IOW is it fine to call webView.load() before answering the request?


Cheers,

--
Caio Marcelo de Oliveira Filho
OpenBossa - INdT