[Webkit-unassigned] [Bug 249778] New: [iOS] Need API to detect the completion of iframe navigations

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Dec 22 09:06:58 PST 2022


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

            Bug ID: 249778
           Summary: [iOS] Need API to detect the completion of iframe
                    navigations
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit API
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: ajuma at chromium.org
                CC: achristensen at apple.com, beidson at apple.com

Currently, WKNavigationDelegate only gets didCommit callbacks for main frame navigations. This means that WKWebView embedders have no way to detect the end of an iframe navigation.

However, iframe navigations can still add an item to WKBackForwardList. Since WKBackForwardList.currentItem is not KVO-compliant, there's no way for an embedder to get a callback when such a navigation item is added.

This means that embedders (like Chrome on iOS) that depend on performing computation to determine feature availability (like autofill) when the current item changes have breakage on iframe-only navigations that add a navigation item, since that navigation item is silently added (see crbug.com/1361722 for how this breaks autofill in Chrome).

It would be useful to either get the full set of navigation callbacks for iframe navigations (these already exist as SPI in WKNavigationDelegage), or to make WKBackForwardList.currentItem KVO-compliant.

-- 
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/20221222/96ea2cad/attachment.htm>


More information about the webkit-unassigned mailing list