Increasing either 'Lightness' or 'Brightness' above zero or ๐ ๐creasing 'Contrast' ๐๐๐๐๐ค zero reduces transparency and starts turning even fully-transparent pixels opaque
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Pinta |
Triaged
|
Undecided
|
Unassigned |
Bug Description
Really simple, so I don't think I need to record a video (but let me know if you do want one!), and it occurred with the flatpak of Pinta 2.1.1 on both the live ISO of Linux Mint 21.3 Cinnamon and an installed copy of Linux Mint 20.3 Xfce.
But as for the issue, this is easily verified by just making a new layer (which always defaults to being fully transparent) and then deleting all other layers, leaving you with only that newly-created fully transparent layer.
From there, I've found that any of the following three things will result in transparency is turning more and more opaque:
"Adjustments" โถ "Hue/Saturation" โ set 'Lightness' to a value greater than zero
"Adjustments" โถ "Brightness/
"Adjustments" โถ "Brightness/
The thing is though, doing the opposite does not do this. That is, your fully transparent layer will remain fully transparent if you set 'Lightness' to less than zero, set 'Brightness' to less than zero, or set 'Contrast' to greater than zero.
description: | updated |
description: | updated |
description: | updated |
summary: |
- Increasing lightness above zero reduces transparency and starts turning - even fully-transparent pixels opaque + Increasing either 'Brightness' or 'Lightness' above zero or ๐ ๐creasing + 'Contrast' ๐๐๐๐๐ค zero reduces transparency and starts turning even + fully-transparent pixels opaque |
description: | updated |
summary: |
- Increasing either 'Brightness' or 'Lightness' above zero or ๐
๐creasing + Increasing either 'Lightness' or 'Brightness' above zero or ๐ ๐creasing 'Contrast' ๐๐๐๐๐ค zero reduces transparency and starts turning even fully-transparent pixels opaque |
description: | updated |
description: | updated |
This is probably the cause of the behaviour seen in bug 2051431