Page Building Image Cropping Issue

We're having an issue with the image cropping tool in the new Page Builder. The crop set in the dialog is not reflected in the page builder or in the published website.

Crop being set in the dialog:

Output of that same crop:

Note in both screenshots I'm looking at the "xs" version of the image.

Thanks!

Hi @nathan,

Thanks for reporting this issue! I'll share it with the Page Builder Team. In the meantime, you can try using the kebab menu in the top-right corner to switch to the Legacy Builder and see if the crop works as expected.

Sam

Hi @nathan,

I'm trying and failing to reproduce this issue. Is there anything unique about the error? Does it occur in a specific flow or with a specific file type?

Sam

Thanks for taking a look @samlittlefair!

In our case we're only moving the image to the right by ~20px, looking at the transform on that element. When we only move it a small amount like this then the crop is not correct, but if we move it all the way to an edge it works and the crop is correct.

If it's helpful I can send an invite to the repo to take a look. Or if there is any other info that would be helpful, let me know.

Hi Nathan,

Sorry for the pause on this one. Work on the Page Builder is ongoing, so it's possible that this bug will disappear eventually. Are you still seeing this behavior? If so, please do invite me to your repository so I can take a closer look. My email has a period between my first name and last, at prismic dot io.

Sam

No worries, Sam.

I took another look and the issue seems to have resolved itself. All good.

Thanks for following up!

That's great to hear! Thanks for the update.

I am also having this issue, including on the "main" version of the image, where the image's final crop is completely different from the crop I've indicated in the pop-up window. This is super annoying and makes cropping images a nightmare since you have to crop and then exist the modal to see the actual output of the crop, which is nothing like what I indicated.

In addition, clicking the "Crop & Resize" button again will completely change the crop in the window. I can adjust the crop little by little by just clicking "Crop & Resize" and closing the modal over and over without moving the image at all.

Can confirm the same issue on one of our repositories (but not all of them).

Hi @amanda / @bsp , can you send me a DM with the names of the repos where this is happening?

Best,
Guy

Hey we see the same bug when using crop and scaling on responsive versions. Position and scale on version is not the same if image editor is opened again. Please see linked video which shows the error.

Thanks!
Lukas

Hi @software ,

Are you seeing this on one or all of your repos?

Hey @Phil I didn't test all of our repos, But it did NOT happen in the one repo I tested.

OK, can you record it with Jam next time you see it?

It will help us recreate and debug this faster.

Thanks.

Sure,
https://jam.dev/c/a9525ff6-d9ff-4a95-b33e-74dd395599f8

Thanks :slight_smile:

We'll get back once we know more.

1 Like

Hey @Phil Is there any update?

We experienced also an similar bug/error. When we update a document with an image trough the migration API the edit part of the images gets updated and pushed correctly but is not applied after publishing the migration release.
You first have to open the crop editor of the image inside the migration release, do some small change, save the document and then publish it. Then the cropping/positioning is correct.

Any help would be really welcome!

Hi @software ,

For the original issue, we've begun tracking it here:
https://prismic.atlassian.net/browse/BT-167?atlOrigin=eyJpIjoiMDg3NzgxY2ViZmY5NDFhZGEwMTQzZjA3NmVhYmY4MDAiLCJwIjoiaiJ9

And for the migration issue, we are aware of it and we've been tracking it for a while here:
https://prismic.atlassian.net/browse/BT-107?atlOrigin=eyJpIjoiODM0NzRhMjUwYjNhNDQyNGE5ZmIyNDU4YjVkMDAwN2EiLCJwIjoiaiJ9

There's no workaround for this issue yet.

Thanks.

Thanks a lot for the updates @Phil

1 Like

Hi everyone. We deployed a fix for this. Let us know if you're still seeing this issue. Thanks :pray:

3 Likes