-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Image attachments hosted in s-ul.eu
do not show in game
#30791
Comments
Both of these shown on the screenshot are gifs. Support for gif display has been considered out of scope previously. Not sure if anything changed. |
Emoji support is a different matter entirely, not one that should be in this thread. |
Both of the examples you attached above contain images hosted on the s-ul.eu domain. Those fail the SSL handshake, therefore not loading in the game:
This can also be confirmed in the logs you have attached:
may need @ppy/team-client attention since s-ul.eu is commonly used by the osu! community as far my quick google and discord searches go, although I'm not quite sure what can be done from our side to fix this (other than to figure out how it still loads on osu-web and in browsers in general). |
s-ul.eu
do not show in game
No image should ever be requested directly from a third party domain. What the hell is going on here?? @ppy/team-web are comment images not being proxied? |
oh yeah, markdown images are proxied on web during parsing phase which for comments happens on frontend (proxied url is obtained through edit: it's only for chat and beatmap discussion but the principle is the same. raw markdown has the original url and only proxied during parsing - either by backend (returning raw html) or frontend |
Hmm, right. We need to be doing that in the client then 💦 |
Type
Game behaviour
Bug description
Open in-game beatmap listing --> go to a beatmap comment w/ image or gif
Beatmap in my example
Screenshots or videos
Version
2024.1115.3-lazer
Logs
compressed-logs.zip
The text was updated successfully, but these errors were encountered: