Unexpected results with w_auto:breakpoints and c_pad

Sebastian

December 16, 2018 17:38

Hi there,

we make heavy use of the auto breakpoint calculation and run into an issue.

Our source image is upright, e.g. https://res.cloudinary.com/demo/image/upload/lady.jpg  (667x100px) and we want to have a square image with crop: pad.

This works via: https://res.cloudinary.com/demo/image/fetch/ar_1:1,c_pad/https://res.cloudinary.com/demo/image/upload/lady.jpg  (1000x1000).

Now we want to calculate the perfect breakpoints for our srcset. For this we add a transformation w_auto:breakpoints like this:
https://res.cloudinary.com/demo/image/fetch/ar_1:1,c_pad/w_auto:breakpoints_320_2000_25_6:json/https://res.cloudinary.com/demo/image/upload/lady.jpg 

Result: The biggest breakpoint is 667px (which is the max width of the source image).
Expected result: The biggest breakpoint is 1000px (which is the max width of the image after the previous transformations).

Of course we want to have https://res.cloudinary.com/demo/image/fetch/ar_1:1,c_pad/w_1000/https://res.cloudinary.com/demo/image/upload/lady.jpg  as biggest image in the website and not https://res.cloudinary.com/demo/image/fetch/ar_1:1,c_pad/w_667/https://res.cloudinary.com/demo/image/upload/lady.jpg 

Is this a Cloudinary bug or a misuse? Any ideas?

Thank you in advance!

Best,
Sebastian

0

• 

  Stephen Doyle

  December 19, 2018 12:05

  Hi Sebastian,

  I've had a look at your example, replicated it, and it appears to be a bug with the breakpoint calculation when the image was padded to be larger than the original width.

  I'm going to raise this issue with our product development team and ask them to investigate further and to resolve it.

  I will provide further updates here as I have them

  Thanks,

  Stephen

  0
• 

  Sebastian

  January 14, 2019 08:40

  Hi Stephen,

  thank you for looking into this!
  
  Do you have any news on this?

  Best regards,
  Sebastian

  0
• 

  Stephen Doyle

  January 16, 2019 19:15

  Hi Sebastian,
  
  The issue is assigned to a member of the product team to investigate and resolve the root cause, but I'm afraid at this time I don't have an estimate for when we'll have a resolution.
  I've linked this post to the internal task tracking the issue, so I'll be sure to let you know once I have a more significant update.
  Regards,

  Stephen

  0
• 

  Sebastian

  January 16, 2019 19:30

  Hi Stephen,

  I don't want to put pressure on you, but for us it's a very annoying and important bug and I'm a little bit disappointed because of the low priority it seems to have in your team. We use Cloudinary in several projects of our clients - several Plus and Advanced (Extra) plans - and the main reason for this decision was your breakpoint calculation which is not working correctly.

  I would appreciate if you can provide a schedule and regular updates on this issue.

  Thank you!
  
  Best,
  Sebastian

  0

Post is closed for comments.