ImageSharp processor renders an element that is not part of the original image.

[vlaellayug]

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

13.3.0

Bug summary

When adding parameters on the original image URL adds an element that is not part of the original image.

Specifics

Might be an issue with ImageSharp? I can see that Umbraco.Cms.Imaging.ImageSharp depends on the following packages:

SixLabors.ImageSharp 3.1.3
SixLabors.ImageSharp.Web 3.1.0

and there's new versions available

SixLabors.ImageSharp 3.1.4
SixLabors.ImageSharp 3.1.2

Steps to reproduce

I have two images where I can reproduce the error.

1.)

Add any correct parameter on the media URL e.g media/3i2ao1cw/test.jpg?quality=75

It will add this gray element:

2.)

Add any correct parameter on the media URL e.g media/dyopjzfj/test.jpg?quality=75

It will add this gray element:

Expected result / actual result

No response

[github-actions]

Hi there @vlaellayug!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[skttl]

This is a bug in ImageSharp, that is fixed in the latest version of ImageSharp