-
-
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
Impossible to use window.open during page load. #4940
Comments
I had to disable popup blocking all together to make it work: cefSettings.CefCommandLineArgs.Add("disable-popup-blocking"); |
I've updated the
It's very unlikely this is a
Please retest with |
I'm a little confused, for me in 128 version, the alloy style is no more available ? |
Alloy was split into runtime component and a 'style' component. The style component still exists on top of chrome to make it work much like the old alloy mode with the new runtime. While 128 killed off the old runtime the style still exists. |
Ok , thanks for explanation ! So I tested the cefclient.exe with the '--use-alloy-style' and the problem occur too , worse it crash when the popup appear ! In any case, with the "disable-popup-blocking" option, on my CefSharp project it work like a charm ! Thank for the help :) |
You can also allow specific origins to create popups using (C++) code like the following in
|
Is there an existing issue for this?
CefSharp Version
126.2.180 or later
Operating System
Windows 10
Architecture
x64
.Net Version
4.8
Implementation
WinForms
Reproduction Steps
Start load this page :
Expected behavior
A new window is create directly when the first window.open call is made.
Actual behavior
window.open return null during 4-5 second, no window is created and it work after.
Regression?
It work with ALLOY Runtime
Known Workarounds
None since 128
Does this problem also occur in the CEF Sample Application
No
Other information
The problem is present on the Minimal CEF Sharp Application but it work with the minimal CEF Client.
The problem is so on the C# implementation side.
The text was updated successfully, but these errors were encountered: