marco: Screenshots of installation windows haven't a transparent background

[InfoLibre]

In MATE version, the "Take Screenshot" or "Kazam" applications don't take screenshots of installation Windows with transparent background.
Example : see joined file. It's the screenshot of an installation window. The up right and left corners are round. The background around these corners should be transparent but it's black (because black is the color of the Mint MATE desktop).
Is it a bug or is it because I'm installing Linux Mint MATE in VirtualBox ?

[corbin-auriti]

How are you taking a screenshot? When I choose grab the current window I get a small border of what was behind it. If you're using Kazam, then it's not related to Mate or Mint

[InfoLibre]

I grab the current window with "Take Screenshot", available in Linux Mint MATE live ISO.
After, I tested with the package Kazam that I installed in the live system, the problem is the same with the 2 softwares.

[InfoLibre]

With "Take Screenshot", I had this results too :

It's like the shadow of the windows is captured too.

[corbin-auriti]

I believe this works as intended. If you need it transparent you may have to use a third party tool or image editing software

[InfoLibre]

It's a joke ?

[corbin-auriti]

I'm sorry, is all your referring to the black pixels? I thought you meant it should have an alpha value. From the looks of your other screenshots I don't see the black pixel, so it seems might have been the virtualbox or compositor you're using.

[InfoLibre]

A window screenshot on my real computer, with "Take Screenshot", Linux Mint MATE 19.2 :

No colored pixel in the corner, no shadow and a transparent background. Impossible to do that with Linux Mint MATE 19.3 in VirtualBox.

[clefebvre]

@monsta you mentioned an issue with invisible borders in Marco 1.22.2? Could this be related?

[monsta]

Yes, it's due to invisible borders 🙁

[monsta]

See also mate-desktop/mate-utils#236

[clefebvre]

Ok, it's not a release blocker on our side so I'll close this. We'll push the fix as an update if we manage to fix it upstream in MATE 1.22.