microsoft / WindowsCompositionSamples

The Windows Composition Samples have moved here: https://github.com/microsoft/WindowsAppSDK-Samples/tree/main/Samples/SceneGraph
https://github.com/microsoft/WindowsAppSDK-Samples/tree/main/Samples/SceneGraph
MIT License
1.12k stars 287 forks source link

Host BackdropBrush glitch under TitleBar area (happens in Groove too) #273

Closed Sergio0694 closed 6 years ago

Sergio0694 commented 6 years ago

Issue Type

[X] Bug Report [ ] Feature Request [ ] Sample request
[ ] Documentation issue or request
[ ] Other – Please describe:

Current Behavior

Hello, this bug has been around for a while now (I've noticed it since the Creators Update, but it's possible it has been there since the CompositionBackdropBrush APIs have been introduced back in earlier W10 releases as well (maybe since the Anniversary Update). The problem is that when using a CompositionBackdropBrush (I've only noticed this glitch when the brush is sampling from the desktop, so when using Window.Current.Compositor.CreateHostBackdropBrush) in an application, if the brush is applied to an area that is behind the TitleBar area, with the TitleBar itself that's hidden (using the ExtendViewIntoTitleBar property), the brush has a grey overlay in the area where the TitleBar would have been. I understand it's not a 100% clear explanation, so here's a screen:

image

NOTES:

I couldn't make a screenshot from Groove (unfortunately I couldn't reproduce the glitch there after the first time it happened), but it looked something like this (it is slightly exaggerated here):

image

Expected Behavior

The host backdrop acrylic brush (and the actual CompositionBackdropBrush brush) should not present these kind of glitches when displayed over (or behind actually) the TitleBar area.

Steps to Reproduce (for bugs)

Either install the latest Groove version and look at the top left TitleBar area, or create an empty app with an acrylic brush, expand the UI into the TitleBar and look at the blur effect right under the TitleBar area.

NOTE: for some reason it looks like this bug most of the times is only visible at the first startup of aa given app, while the same APIs work fine after that. As an example: I've noticed this glitch in Groove right after updating it, but after that it worked fine. Same with my app (OneLocker): I've deployed it from VisualStudio, opened it, noticed the glitch, closed and reopened it and the brush was working fine.

Your Environment

krenner commented 6 years ago

Hi Sergio0694 - Thanks for the detailed write up. I am happy to report this bug has been addressed and should be resolved in subsequent insider builds.

Sergio0694 commented 6 years ago

@krenner Hello, thank you for your answer, glad to hear it's already been fixed! πŸ˜„ And wow, that was fast, were you already aware of this issue or was it just really easy/quick to fix?

I'm looking forward to the next RS4 builds then, thanks again!

krenner commented 6 years ago

This was a known bug. The details you provided in your post made it easy for us to make the connection. The fix should be current insider builds now so I am going to mark this issue as closed. Please let us know if you see any more problems.