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

WebView2 runtime creates a black screen or black band when closing a PWA when a notification is given in response for closing the app. #4349

Closed
PCRacer opened this issue Feb 6, 2024 · 2 comments
Assignees
Labels
bug Something isn't working regression Something used to work but doesn't anymore

Comments

@PCRacer
Copy link

PCRacer commented Feb 6, 2024

What happened?

WebView2 displays black background after Notification popup when closing a PWA app that gives a response notification when closing the app.

On a secondary monitor the whole screen goes black with the notification not centered!

WebView2.Display.render.In.Main.Screen.Not.Working.webm

When reproducing the error on my main monitor, the WebView2 display moves down the height of the notification and the stays there without moving when navigating to another website.

WebView2.Display.Render.Not.Working.webm

This error cannot be reproduced in Edge or Chrome, so it is the WebView2 runtime itself that is to blame.

When opening a new tab, WebView2 is working correctly again.

Importance

Moderate. My app's user experience is affected, but still usable.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

121.0.2277.106

SDK Version

1.0.2277.86

Framework

Win32

Operating System

Windows 10

OS Version

19045.3996

Repro steps

  1. Start the browser application.
  2. Navigate to https://developer.mozilla.org/en-US/docs/Web/API/Window/beforeunload_event
  3. Enter any value into the form in the middle of the page
  4. Press the Reload button
  5. The WebView2 windows moves down and to the right inside of the bounds of the parent window (empty borders are created on the top and on the left side)
  6. If you cancel the following dialog and press Reload again the WebView2 window even moves further downwards each time (also the following dialog)

Watch the two videos to reproduce the error... One is the main monitor and the other is from a second monitor which gives two different errors.

One video shows when using the app on a second monitor and one error is shown on the main monitor, which gives two different display errors!

Navigate to any website that has a notification response when closing... e.g. https://desktop.ssuiteoffice.com

An app or any must be opened to activate the notification when closing or navigating to Home page.

WebView2.Display.Render.Not.Working.webm

This error is given when used on the main monitor...

WebView2.Display.render.In.Main.Screen.Not.Working.webm

This error cannot be reproduced in Edge or Chrome, so it is the WebView2 runtime itself that is to blame.

Repros in Edge Browser

No

Regression

Regression in newer Runtime

Last working version (if regression)

SDK 1.0.2210.55 Runtime 121.0.2210.55

@PCRacer PCRacer added the bug Something isn't working label Feb 6, 2024
@github-actions github-actions bot added the regression Something used to work but doesn't anymore label Feb 6, 2024
@PCRacer
Copy link
Author

PCRacer commented Feb 6, 2024

Please download the application for testing purposes...

Download Link in text:
https://www.ssuiteoffice.com/downloads/apps/SetupSSuiteNetSurfer64X.exe

@champnic
Copy link
Member

champnic commented Feb 6, 2024

Thanks for the bug report @PCRacer! We are able to reproduce this issue locally, and are currently tracking it in #4350, so closing this one as a dupe (apologies they are technically out of order).

@champnic champnic closed this as not planned Won't fix, can't repro, duplicate, stale Feb 6, 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 regression Something used to work but doesn't anymore
Projects
None yet
Development

No branches or pull requests

4 participants