Spaces:
Running
Seemingly not functional on mobile devices
Hello there, this is a great resource, very nice work. When I use this space on a PC, it works fine, the the output occasionally freezes and forces me to reload the page from time to time. Unfortunately, for am unknown reason, on mobile devices, the output seems to be unable to display the character tags once it finishes loading, merely displaying the character drop down bar with no actual output, whereas if this was on PC, the output would display fine, (for example, inputting "Naruto" as the query would return character tags in all three categories on PC, but on mobile, nothing shows). Even changing the web page to display in desktop mode cannot make the output work.
On am unrelated note, may I suggest that you link an example AI model that would be compatible with a particular character tag when one clicks on the tag entry? Such as linking to an Illustrious model when clicking on an Illustrious compatible character tag so people can try them out immediately and efficiently?
Hello. Is it a bug in Gradio, the GUI library...?
I tried changing to a slightly older version.
I am unsure, as no actual error is displayed, the output element simply fails to load the character tags that I know load fine on PC. As I am not the space owner, I cannot look at the logs of the actual generation process to see what, if any errors are popping up. I just attempted to see if it is functional and it is still not working. If you are on mobile you can probably see for yourself what I mean with what is happening, assuming it isn't an issue unique to me for an unknown reason.
Firefox for Android works fine...
Spaces in HF tends to have problems on the iPhone, but I wonder if that's it?
Anyway, it seems to be an issue that depends on the environment, but when we look into things properly, these kinds of things are usually troublesome bugs...
Apologies for the late response. I utilize Brave browser on both PC and Android. Brave browser is based on chromium, and I can confirm that both the actual Chrome browser and Brave are not displaying the space correctly for me on mobile, despite the space working as intended on PC. I am unable to confirm if this is a problem unique to me, but if it is working for you, then maybe it is something about my phone that is preventing function, though I cannot say what as I do not know what the root cause could be.
I'll try Brave later.
It worked with the Brave browser on Android...
Is AdGuard or something like that installed?
It seems that the HF sometimes behaves strangely due to browser cookie settings, including on PCs.
I have something similar to AdGuard called AdAway, which is a third party app that blocks ads across all apps, not just browsers. I've disabled it to make sure it is not interfering with the space's functionality, but the issue persists on my end. Here is a screenshot from my perspective. The last thing I can try is to restart my phone to refresh the cache and see if that changes anything.
Update: restarting my phone did nothing to fix the issue, it appears that my phone simply refuses to display the output upon searching a tag, which is strange because the first two default examples load perfectly.
Thank you. The verification is helpful.π It seems that something is definitely having an effect.
I don't know how much of the responsibility is Brave's and how much is Hugging Face's, but it's a two-way street or complicity.
I'll try messing around with Brave's settings later. I originally installed Brave, but I only use it as a sub, so it's mostly the default settings.
Edit:
If I set βTurn off JavaScriptβ in Brave, it won't work, but otherwise it seems to work even if you set strict privacy settings. Maybe it's not Brave, but something on your smartphone (such as the communication line or Google-related services) that doesn't get along with HF. I haven't tried a VPN because they're paid, but I'm guessing you don't use one either.π
Right now, there is a network problem between a specific service and HF, and it's not impossible to deny a connection to that.
Well this is embarrassing, it turns out it does work on mobile. Apparently, the tags are very strict when it comes to how one types the query, as the tags are case sensitive. For example, typing "Naruto" did not work, but "naruto", without capitalization, does. Perhaps you can update the search logic so that things like this don't prevent the display of the output list.
Oh, I'm lucky if it wasn't an error. By the way, the case-sensitivity distinction is a bug.
I was trying not to distinguish at first, but that code disappeared somewhere along the way.
Anyway, one bug fixed!π