[Webkit-unassigned] [Bug 232506] New: [iOS] Need API for marking file requests as non-app-initiated
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri Oct 29 14:40:00 PDT 2021
https://bugs.webkit.org/show_bug.cgi?id=232506
Bug ID: 232506
Summary: [iOS] Need API for marking file requests as
non-app-initiated
Product: WebKit
Version: WebKit Nightly Build
Hardware: Unspecified
OS: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: Page Loading
Assignee: webkit-unassigned at lists.webkit.org
Reporter: ajuma at chromium.org
CC: beidson at apple.com, bfulgham at webkit.org,
justincohen at google.com, katherine_cheney at apple.com,
rohitrao at google.com
Chrome for iOS uses a file-based session restoration approach for cases where [WKWebView setInteractionState:] cannot be used. These cases include syncing tabs across devices, reopening closed tabs (i.e., where the user closes a tab, but decides later that they want the tab back), and users upgrading from iOS 14.
Network requests in such tabs should be marked as non-app-initiated, but there's currently no way to set request attribution for file requests. The result is that all back/forward and link-tap navigations in such tabs get marked as app-initiated, until the next call to [WKWebView loadRequest:] (in practice, this means that all navigation is marked as app-initiated until the next time the user types a URL in the URL bar instead of tapping on links).
Specifically:
1) [WKWebView loadFileRequest:allowingReadAccessToURL:] only looks at the URL in the given request, and ignores everything else, including the request's |attribution| property.
2) [WKWebView loadFile:allowingReadAccessToURL:] doesn't have any way to set attribution.
--
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/20211029/c8942388/attachment.htm>
More information about the webkit-unassigned
mailing list