We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
131.3.50
Windows 11
x64
.Net Framework 4.8
WinForms
Just access any web pages which has a JavaScript popup and push the button which launches popup.
Get a popup.
Nothing happened.
I guess the problem are from security update on "Chromium" for CVE-2024-7965. Before CVE-2024-7965, there's no such problem.
On JsDialogHandler,
JsDialogHandler.OnJSDialog() { suppressMessage=false; browser.ShowDevTools(); browser.CloseDevTools(); return false; } I get popup.
JsDialogHandler.OnJSDialog()
{
suppressMessage=false;
browser.ShowDevTools();
browser.CloseDevTools();
return
}
Not Tested
Again, I guess the problem are from security update on "Chromium" for CVE-2024-7965. Before CVE-2024-7965, there's no such problem.
The text was updated successfully, but these errors were encountered:
Same problem here, the Workarounds is really weird ....
Sorry, something went wrong.
No branches or pull requests
Is there an existing issue for this?
CefSharp Version
131.3.50
Operating System
Windows 11
Architecture
x64
.Net Version
.Net Framework 4.8
Implementation
WinForms
Reproduction Steps
Just access any web pages which has a JavaScript popup and push the button which launches popup.
Expected behavior
Get a popup.
Actual behavior
Nothing happened.
Regression?
I guess the problem are from security update on "Chromium" for CVE-2024-7965.
Before CVE-2024-7965, there's no such problem.
Known Workarounds
On JsDialogHandler,
JsDialogHandler.OnJSDialog()
{
suppressMessage=false;
browser.ShowDevTools();
browser.CloseDevTools();
return
false;}
I get popup.
Does this problem also occur in the CEF Sample Application
Not Tested
Other information
Again, I guess the problem are from security update on "Chromium" for CVE-2024-7965.
Before CVE-2024-7965, there's no such problem.
The text was updated successfully, but these errors were encountered: