Hi @thomas.digregorio , thanks for raising the issue. This wasn't on our radar so I'm following up with the team now. I don't think it is related to the fact you are using the Legacy Editor but I'd be happy to upgrade you and see if that resolves the problem?
the media library, for all images as far as I can tell
some images of the front end (given by the API)
As mentioned above, we rework those URL params programmatically. Because of this double auto
param in the original URL of the image, we're not getting the rect property when we re-integrate this param.
For instance, the hero image on this page is rendered at 1080x720, where it should be 1080x560 thanks to the rect param
Yes, the behavior has been removed as part of the bug I was describing.
The hero image of this page has this URL retrieved from Prismic: https://images.prismic.io/360learning/Zlbqw6WtHYXtT4aZ_FR-Blog-b-corp-rse.jpg?auto=format,compress?auto=compress,format&rect=0,284,3840,1991&w=1080&h=560
You can see the double auto parameter there
As I mentioned, we rework programmatically this URL so that it becomes this one: https://images.prismic.io/360learning/Zlbqw6WtHYXtT4aZ_FR-Blog-b-corp-rse.jpg?auto=format&fit=max&fm=png&q=75&dpr=1&w=1080
for that we first retrieve the parameters from the original url using url.split("?")[1]
as you can guess, doing that will get only auto=format,compress & completely ignore this part auto=compress,format&rect=0,284,3840,1991&w=1080&h=560, which is of interest to us
for the rest of the params
auto is removed (the default one)
auto, fit, fm, q, and dpr are added as new default params
w=1080 is defined in the code on our end
So we completely lose the params defined in the Prismic image crop tool, like rect, which messes up the final render of our image