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
tl;dr It might be good to encode commas in cloudinary URLs as %2C except f_auto
I had the issue that Chrome was not picking up the correct image from the srcset. And I found these two interesting things:
Media queries in sizes attribute work exactly same as CSS media queries. So first valid media query, reading from left to right will be applied. Funny thing browser does (Chrome at least), if one query between set of commas is invalid it won't invalidate whole sizes attribute, just that query.
Commas can indeed be encoded in Cloudinary URLs in most places without any issues. However, in conjunction to f_auto, existing commas should remain unencoded at the moment.
Nevertheless, there is a quick and easy workaround for this. Just replace the comma that is after f_auto with a solidus (slash - /) sign and it will work: https://res.cloudinary.com/endjin/image/upload/f_auto%2Cq_70%2Cw_512/v1590614405/assets/images/blog/2020/05/header-depositing-cheques-via-a-mobile-banking-experience-1024px.png
tl;dr It might be good to encode commas in cloudinary URLs as %2C except f_auto
I had the issue that Chrome was not picking up the correct image from the srcset. And I found these two interesting things:
https://stackoverflow.com/a/55240049/10316085
https://support.cloudinary.com/hc/en-us/community/posts/360008383359-Encoding-Commas-in-the-URL-changes-behaviour
I solved it with adding a filter, and it started picking up the correct image from the srcset
The text was updated successfully, but these errors were encountered: