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.

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

CoreWebView2.NewWindowRequested not fired when tab opened by extension #3841

Closed
RendijsSmukulis opened this issue Oct 3, 2023 · 2 comments
Closed
Assignees
Labels
bug Something isn't working tracked We are tracking this work internally.

Comments

@RendijsSmukulis
Copy link

RendijsSmukulis commented Oct 3, 2023

Description

  • CoreWebView2.NewWindowRequested does not fire when an extension calls chrome.tabs.create. This means a webview2-owned window opens with the site, rather than allowing the host application to handle this request.

Version
SDK: 1.0.2106-prerelease
Runtime: Version 117.0.2045.47 (Official build) (64-bit)
Framework: WPF
OS: Win11

Regression
Was this working before but has regressed? No.

Repro Steps

Expected:

  • CoreWebView2OnNewWindowRequested handler fires, and no new window is shown

Actual:

  • Website opens in a "webview2 window", and can't be "owned" by the application.

AB#47326790

@RendijsSmukulis RendijsSmukulis added the bug Something isn't working label Oct 3, 2023
@dianaqu
Copy link
Contributor

dianaqu commented Oct 3, 2023

Thanks for reporting the issue. Let me try repro first.

@dianaqu dianaqu added the tracked We are tracking this work internally. label Oct 30, 2023
@dianaqu
Copy link
Contributor

dianaqu commented Feb 7, 2024

Hi. This issue is fixed with Canary 123.0.2389.0

@dianaqu dianaqu closed this as completed Feb 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working tracked We are tracking this work internally.
Projects
None yet
Development

No branches or pull requests

2 participants