Skip to main content
John_Carney
Participant
December 21, 2022
Question

Search by Image link broken?

  • December 21, 2022
  • 1 reply
  • 582 views

The Search by Image link seems to be broken. This is on the main fonts.adobe.com page. I will try the Capture app instead.

    This topic has been closed for replies.

    1 reply

    Tarun Saini
    Community Manager
    Community Manager
    December 22, 2022

    Hi there,

     

    Could you please tell us what's happening when you're trying the search by image option on the fonts.adobe.com page? Did you try another web browser? Are you getting any error messages? We're here to help, just need some info.

     

    Regards,

    Tarun

    John_Carney
    Participant
    December 22, 2022

    Hi Tarun,

    Thanks for getting back to me. I have attached an image of 4 screenshots. This appears to be happening on mobile device for both Safari and Chrome browsers. (I have an iPhone 11 Pro with all updates.) The first screen is me pressing and holding on the Browse All Fonts button. It shows me a preview of the link. The second screen is me pressing and holding on the Search by Image button. No link. And pressing and releasing does nothing. I did the same tests for the Chrome browser. But I think I know what you all changed. Before an update you must have pushed through, the Search by Image button went to another page or popup where you could choose to upload an image. Now, on desktop, it appears you have bypassed that page/popup and are triggering an action to open up Finder or Explorer. This action is not being implemented on the mobile devices. I would expect something to pop up from the bottom asking me to browse in my Photo Library or Files or Creative Cloud. This is as far as my knowledge extends with code. I hope something I have said or shown helps you find the bug. In the meantime, I know it works on desktop. All is well. Have a great day!

    Tarun Saini
    Community Manager
    Community Manager
    January 3, 2023

    Thanks for your response @John_Carney 

     

    I was able to reproduce the issue, and I have escalated the case to our product team, who will look into this. I will keep you posted once I hear anything from them.