This support forum is no longer in use. Please use the Cloudinary Community at https://community.cloudinary.com/ to receive assistance from other members of the community and from Cloudinary's support team. For account-specific questions or if you believe that you've encountered a bug, please contact the Cloudinary team directly via the "submit a request" option on this support site.

Not showing close button Mobile widget v2

Comments

11 comments

  • Official comment
    Avatar
    Daniel Mendoza

    Hi

    This issue should now be resolved. Please reach out to us if you see otherwise.

     

    Comment actions Permalink
  • Avatar
    Aleksandar Kostadinov

    Hi,

    Thanks for your message.

    This is not in the specification and is definitely a bug. I've raised this with our team who are working on adding a fix. In some cases, hitting the back button on mobiles allows users to close the Widget.

    I will keep you updated on the progress of the fix.

    Best regards,

    Aleksandar

    0
    Comment actions Permalink
  • Avatar
    Thomas

    Any update on this? Hitting the back button either does nothing, or it takes you back out of the app, instead of back to the actual page that you were on.

    0
    Comment actions Permalink
  • Avatar
    Aleksandar Kostadinov

    Hi Thomas,

    Our team have added a fix and this is now being reviewed and tested. Once it gets the nod of approval we'll have an idea in terms of ETA for deployment. I'll share that as soon as we have it.

    Best regards,

    Aleksandar

    1
    Comment actions Permalink
  • Avatar
    Ben

    Where can we go to find out when new releases are available? Also looking for this issue to be resolved.

    0
    Comment actions Permalink
  • Avatar
    Aleksandar Kostadinov

    Hi Ben,

    We will update this thread as soon as there's an ETA for release.

    0
    Comment actions Permalink
  • Avatar
    Olivier Mills

    Any update? Its been 2 months and without a close button it makes the widget not usable on mobile.

    0
    Comment actions Permalink
  • Avatar
    Frank Geertsma

    +1

    0
    Comment actions Permalink
  • Avatar
    Aleksandar Kostadinov

    Hi Olivier, Frank,

    A fix was added, however, it didn't pass all required QA tests and thus is back in dev at the moment. Apologies for the delay on this.

    0
    Comment actions Permalink
  • Avatar
    Jared Neff

    Any update to this? It's been a month since last word and still an issue for us. 

    0
    Comment actions Permalink
  • Avatar
    Jared Neff

    Sorry, I see that it is resolved now. Thank you for the update!

    0
    Comment actions Permalink

Post is closed for comments.