-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
WinForms - A window.confirm() dialog generated by this page was suppressed because this page is not the active tab #4976
Comments
Have you confirmed this exists in the current supported version?
The |
Testing with
Clicking on the
Opening Behavior appears to be consistent with the Making this as |
Appears that chromiumembedded/cef#3818 is the correct Closing as upstream |
Testing with You can set the following before you create a
|
Switching to a |
Is there an existing issue for this?
CefSharp Version
126.2.180
Operating System
Windows 10
Architecture
x64
.Net Version
.Net 4.8
Implementation
WinForms
Reproduction Steps
CefSharp.WinForms.Example
, open the following webpage: https://googlechrome.github.io/samples/block-modal-dialogs-sandboxed-iframe/window.confirm("Hello")
buttons.Expected behavior
A confirm dialog opens.
Actual behavior
The dialog does not open, and the following message appears in the status bar:
Regression?
In version 124.x, this was working, likely because it still used the Alloy style by default.
Known Workarounds
If the Alloy style is used with
CefSettings.ChromeRuntime = false
, the dialog opens as expected.However, Alloy style has another issue that can be resolved by upgrading to Chromium Runtime, and since it is now deprecated, I don’t consider this a valid workaround.
Does this problem also occur in the CEF Sample Application
No
Other information
I tested this in the Cef Sample application, and it worked fine there. The dialogs opened even when I ran
cefclient.exe
without the--use-alloy-style
flag. Therefore, I believe this is not an issue with CEF itself, but with CefSharp.However, I found similar issue here:
But I couldn't replicate it in the CEF sample application. The issue only occurs in
CefSharp.WinForms.Example
.The text was updated successfully, but these errors were encountered: