[Webkit-unassigned] [Bug 174170] New: Do not pass API::FrameInfo for source frame or clear out page of target frame on API navigation
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Jul 5 12:33:45 PDT 2017
https://bugs.webkit.org/show_bug.cgi?id=174170
Bug ID: 174170
Summary: Do not pass API::FrameInfo for source frame or clear
out page of target frame on API navigation
Product: WebKit
Version: WebKit Local Build
Hardware: All
OS: All
Status: NEW
Severity: Normal
Priority: P2
Component: WebKit2
Assignee: webkit-unassigned at lists.webkit.org
Reporter: dbates at webkit.org
CC: beidson at apple.com
For an API initiated navigation we pass API::FrameInfo for both the source and target frame that have a null page pointer. This condition is subtle to check for and error prone. It is also unclear how meaningful it is to pass frame info for the source frame for an API-initiated navigation as well as the value of clearing out the pointer for the page in the target page. As a step towards improving the -decidePolicyForNavigationAction: delegate API we should not pass frame info for the source frame and not nullify the page pointer of the target frame when the navigation is initiated by API. An embedding client can then determine that the delegate callback originated from API by checking if we have a non-null source frame. This is unlike to be the last change we make to the design of this callback. We will look to further iterate on this design towards ensuring it is straightforward for an embedding client to determine when -decidePolicyForNavigationAction: is called as a result of an API navigation.
--
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/20170705/af5a63d3/attachment.html>
More information about the webkit-unassigned
mailing list