Hello, On Mon, Oct 24, 2011 at 9:57 AM, Balazs Kelemen <[email protected]> wrote: > It seems to me this assumption is not correct. The appropriate code part is > WebFrameLoaderClient::dispatchDecidePolicyForNavigationAction. It sends a > synchronous message so we need to answer immediately on the UI side:
Yes and no. :-) These comments (and the sync code) were added in the patch for https://bugs.webkit.org/show_bug.cgi?id=53785. But the async API still works: WebPage still handles the async response, and WebPageProxy will still send the response message if the listener is called after returns. Note also the fact that the message returns a boolean and the action, the boolean indicates whether the reply is sync or async. I'm investigating more about the original issue, maybe we could find a way to fix the problem when using the async case, possibly even getting rid of the sync case. Cheers, -- Caio Marcelo de Oliveira Filho OpenBossa - INdT _______________________________________________ webkit-qt mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt
