Bug 174170 – Do not pass API::FrameInfo for source frame or clear out page of target frame on API navigation

• Component: WebKit2
• Status: RESOLVED FIXED

[Daniel Bates]

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.

[Radar WebKit Bug Importer]

<rdar://problem/33140328>

[Daniel Bates]

Created attachment 314642 [details]
Patch and unit tests

[Daniel Bates]

Committed r219149: <http://trac.webkit.org/changeset/219149>