Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Chrome Runtime] Impossible to use window.open during page load. #4920

Closed
1 task done
max3163 opened this issue Sep 5, 2024 · 6 comments
Closed
1 task done

[Chrome Runtime] Impossible to use window.open during page load. #4920

max3163 opened this issue Sep 5, 2024 · 6 comments
Labels
upstream These issues require fixing in the Chromium Embedded Framework(CEF) or Chromium.

Comments

@max3163
Copy link

max3163 commented Sep 5, 2024 •
edited
Loading

Is there an existing issue for this?

  • I have searched both open/closed issues, no issue already exists.

CefSharp Version

126.2.180 or later

Operating System

Windows 10

Architecture

AnyCPU

.Net Version

4.8

Implementation

WinForms

Reproduction Steps

<!DOCTYPE html>
<html lang="en">
  <head>

  </head>
  <body>
    <script>
      let count = 0;
      function openWindowRec() {
        console.log("Try :" + count );
        if (!window.open('', 'ID321')) {
          setTimeout(() => {
            count++;
            openWindowRec();
          }, 500)
        }
      }
    </script>
  </body>
</html>

Load this simple page which try to open a new window.

Expected behavior

A new window is create directly when window.open call is made.

Actual behavior

Actually nothing happen during many seconds, works only after (about) 10-15 seconds.

Regression?

It works perfectly on 125 and with settings.ChromeRuntime = false parameter

Known Workarounds

use settings.ChromeRuntime = false;

Does this problem also occur in the CEF Sample Application

Not Tested

Other information

No response
@amaitland amaitland added the upstream These issues require fixing in the Chromium Embedded Framework(CEF) or Chromium. label Sep 5, 2024
@amaitland
Copy link
Member

If you discover an issue with the Chrome Runtime then you need to raise the issue on the CEF ISSUE TRACKER

https://github.com/chromiumembedded/cef/issues

Then please post a link in #4835

@amaitland
Copy link
Member

Thanks.

For reference chromiumembedded/cef#3785

@max3163
Copy link
Author

max3163 commented Sep 27, 2024

I re-open this ticket because I just test the issue with the CefClient minimal application and it work as expected ! But it's not the case with the C# Minimal Application. So the problem is on CEfSharp side.

@max3163
Copy link
Author

max3163 commented Sep 27, 2024

arf it's not possible to re-open a ticket...????? I will create a new one so...

@amaitland
Copy link
Member

arf it's not possible to re-open a ticket...????? I will create a new one so...

Please don't create duplicate issues. In future please ask for the issue to be reopened.

We don't need unnecessary duplicates.

@max3163
Copy link
Author

max3163 commented Sep 28, 2024

Ok, sorry, next time I will do that.

But, if it's the process, why don't allow to re-open an issue directly ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
upstream These issues require fixing in the Chromium Embedded Framework(CEF) or Chromium.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@amaitland @max3163