Whether this is a usability bug or something else, I'm not sure, but it was very surprising to me. I had unwittingly done half my work on the background layer, then when I came to move and scale it, uncovered this issue: transparent areas of the background layer became white. This can be worked around by copying the layer's contents to a new layer. From a "principle of least surprise" perspective I would say that either the background layer should not accept any kind of transparency, or it should accept it and work as normal. I guess what is happening is that, to support the "infinite canvas of white" feature, Krita is filling in all these pixels on the assumption that they came from outside the bounds of the image. Reproducible: Always Steps to Reproduce: 1. Create a new image 2. Erase some of it in any way you please 3. Scale the image a little with the transform tool Actual Results: The transparent area becomes opaque Expected Results: The transparent area remains transparent
Hi Chris, Thanks for your report. This definitely is a bug -- I'm not even totally sure when it happens exactly, since it doesn't seem to happen if I make the layer entirely transparent then paint a bit, then transform.
Ah, the problem is the default pixel color of the background. An erased pixel doesn't exist anymore, so the transform tool fills in with the default color.
I have to reconsider: this isn't something that can be fixe, because of what I said in the last comment. It is possible to setup an image so that this doesn't happen, with a fixed background color, or just by not working on the solid background layer.