[Webkit-unassigned] [Bug 238838] New: [iOS] Need API on NavigationAction to detect a simulated request

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Apr 5 14:45:53 PDT 2022


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

            Bug ID: 238838
           Summary: [iOS] Need API on NavigationAction to detect a
                    simulated request
           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,
                    bfulgham at webkit.org, cdumez at apple.com

Chrome for iOS is using WKWebView’s loadSimulatedRequest API to display error pages for failed navigations. One reason for a navigation failing is when a URL is blocked by enterprise policy.

In this case, Chrome tries to load a simulated request with an error message, using the URL of the blocked page.

However, in decidePolicyForNavigationAction, the URL blocking logic cannot distinguish a real load of the blocked page vs a simulated request using that URL, since there's no information in the WKNavigationAction to tell us that this is a simulated request.

One way to fix this would be to promote the _mainFrameNavigation SPI in WKNavigationAction to API, so that we can compare that WKNavigation* to the one returned by loadSimulatedRequest.

I've also filed FB9974496 for this request.

-- 
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/20220405/c976fe26/attachment.htm>


More information about the webkit-unassigned mailing list