- Issue created by @Grimreaper
- 🇫🇷France DrDam
@deepali sardana : thanks for the merge Request, but I'll close it, because there is a lighter way to acheive that.
- 🇫🇷France DrDam
In fact, this case is not natively covered by nativ responsiveImage because of the possible mixe between "allow/no-allow" upscaling.
- 🇫🇷France DrDam
The problem is that the imageStyle stack does not provide a simple way of finding the ‘expected size of the derivative if the source image is large enough not to be upscaled’ for an image style.
In fact, it is not possible to ‘classify’ image styles by this ‘expected size’ and therefore to find the ‘smallest’ image style that is most suitable.The anomaly is present in native ResponsiveImages too.
- 🇫🇷France DrDam
Exemple as a native src-set image :
The "tiniest" size ( 100px) better fit for the thumbnail image style are associate with the "wide" image style because it's the "last" of the list.
- 🇫🇷France DrDam
I have rework the "association loop" for trying to manage mixte between not-upscaling / upsaling.
The association between size and imageStyle are "not optimal" because of #10 and #11, but it doesn't really matter because the derivative will be the same, just not in the "best folder" on the disk