Unexpected results with w_auto:breakpoints and c_pad

Comments

4 comments

  • Avatar
    Stephen Doyle

    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
    Comment actions Permalink
  • Avatar
    Sebastian

    Hi Stephen,

    thank you for looking into this!

    Do you have any news on this?

    Best regards,
    Sebastian

    0
    Comment actions Permalink
  • Avatar
    Stephen Doyle

    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
    Comment actions Permalink
  • Avatar
    Sebastian

    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
    Comment actions Permalink

Please sign in to leave a comment.