-
Notifications
You must be signed in to change notification settings - Fork 57
[Problem/Bug]: navigationStarting bypassed by BasicAuth: Basic realm="Web access"" #5152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@dfghj44444 if you are facing the similar issue as #5144. If not, you can reopen it. |
@dfghj44444, I apologize for the inconvenience caused by mistakenly closing the issue. I am reopening the issue and closing #5155 |
Any Update? @dhveerap |
@dfghj44444 Fix for a similar issue was already part of 137 version. Could you kindly verify in 137 Canary to check if this is resolved? |
@dhveerap I tried the canary version 138, and confirmed this issue do not exist any more, this bug could be closed, thanks. |
@dfghj44444 Thanks for the confirmation. Closing the issue. |
What happened?
There's an a link with basic Auth(chanllenge is Basic realm="Web access" )in this page, while I put_canceled in NavigationStartingEvent, the page navigation still goes to navigationComplete.
Importance
Important. My app's user experience is significantly compromised.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
134.0.3124.51
SDK Version
1.0.2210.55
Framework
Win32
Operating System
Windows 11
OS Version
23H2
Repro steps
1.Webview2 Controller add event onNavigationStart add block url: https://testpages.eviltester.com/styled/auth/basic-auth-results.html, if target url is this , ars->put_Canceled(true).
2.Compile and start test exe, start with page https://bing.com, and type "window.location.href='https://testpages.eviltester.com/styled/auth/basic-auth-results.html'" in console.
3.you'll see even the navigationStart callback blocked this navigation, the page still jump out from bing.com, and history changed
Repros in Edge Browser
No, issue does not reproduce in the corresponding Edge version
Regression
No, this never worked
Last working version (if regression)
No response
The text was updated successfully, but these errors were encountered: