WebKit Bugzilla
New
Browse
Search+
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED WONTFIX
300035
Expose WebKit::NavigationActionData::isRequestFromClientOrUserInput through WKNavigationAction
https://bugs.webkit.org/show_bug.cgi?id=300035
Summary
Expose WebKit::NavigationActionData::isRequestFromClientOrUserInput through W...
Brent Fulgham
Reported
2025-10-02 11:26:42 PDT
The NavigationActoinData class contains a flag that hints whether an action was triggered through User Input or a load directive from the User Agent Chrome (NavigationActionData::isRequestFromClientOrUserInput) (e.g.,
Bug 266354
). It would be helpful to expose this in the `WKNavigationAction` layer so that the User Interface could use this as a hint about how verbose to be during certain load failures. For example, a failed load of a custom URL scheme triggered by script while loading or updating a page doesn't generally need to be reported to the user, since they aren't aware of the load attempt and console logging will let a web developer see this. On the other hand, if a user clicks on a link or enters a URL in the browser chrome and the load fails, we want to immediately present this information so the user can understand what went wrong. This patch exposes the existing WebKit::NavigationActionData::isRequestFromClientOrUserInput flag through the WKNavigationAction class so a client can access it. The data is already present in the UIProcess as internal state.
Attachments
Add attachment
proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1
2025-10-02 11:27:44 PDT
<
rdar://problem/161833541
>
Brent Fulgham
Comment 2
2025-10-02 11:30:31 PDT
Pull request:
https://github.com/WebKit/WebKit/pull/51689
Brent Fulgham
Comment 3
2025-10-03 14:26:33 PDT
***
Bug 300040
has been marked as a duplicate of this bug. ***
Brent Fulgham
Comment 4
2025-10-09 14:52:15 PDT
This ended up not being necessary, so closing this.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug