[Webkit-unassigned] [Bug 174531] WebFrameLoaderClient::dispatchDecidePolicyForNavigationAction() may not be able to determine page that initiated navigation

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Jul 14 17:00:20 PDT 2017


https://bugs.webkit.org/show_bug.cgi?id=174531

Geoffrey Garen <ggaren at apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ggaren at apple.com

--- Comment #1 from Geoffrey Garen <ggaren at apple.com> ---
This seems like an OK improvement. But I'm not sure it's necessary.

It's kind of difficult to maintain the plumbing, and test, to be able to identify the original WebView even after a frame has been removed from it.

I don't know of a strong motivating example where original WebView is better than nil for navigations after the source frame has been removed from the WebView. Maybe nil is better for some cases?

Given the difficulty involved, I think it may be better to stick with the existing nil behavior unless / until we come up with a motivating example for something more special.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170715/b972407f/attachment.html>


More information about the webkit-unassigned mailing list