You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Screen shot taken from Safari (15.6) on macOS Catalina (10.15):
BTW, I reported this in issue #104 a couple of days back as follow up comment, seems been slipped due to ticket closed automatically, thus opening the new one instead.
The text was updated successfully, but these errors were encountered:
Thanks for the ping. How do you think we should handle this issue? We could sniff the User-Agent and fallback to default mime-type for the image. Thoughts?
I always handle images with extensions on the web. However, in rare cases like this, options in my mind:
original mime type: mostly jpeg or png, obtained during the upload process
do nothing, as for authors deliberately opt-in to the extensionless practice, and knowingly acknowledge the lack of support for users under Safari & macOS <= 10.15 (via statistics)
sniffing, from the user-agent
I think option 1 is the safe move. For option 2 need some way to inform the authors beforehand. I don't have any experience with Option 3, but it seems to make things even more tricky.
Screen shot taken from Safari (15.6) on macOS Catalina (10.15):
BTW, I reported this in issue #104 a couple of days back as follow up comment, seems been slipped due to ticket closed automatically, thus opening the new one instead.
The text was updated successfully, but these errors were encountered: