Hello, I am not sure that array means what you think it means.
What it means is:
when my viewer screen has a size of 1200px or more use the thumbnail with size xl
when my viewer screen has a size of 1400px or more use the thumbnail with size xxl
And also:
When my screen has a size of 0 or more use thumbnails of size xs.
So when you say “no thumbnail for xs” that is not a correct interpretation of what this array means.
Afixia’s size array in Pagetheme is not in question, rather the thumbnails, automatically created from the install controller. (Github link in first post)
I have installed the @afixia basic bedrock theme. When I look at the thumnails automatically created I have both, handle-xs and handle-sm with 540px, also two thumbnails with identical images sizes. That was my confusion.
According to your array, the created thumbnail image for sm should have 720px not 540px as in afixia’s install controller
Correct?
Reason:
We create presentations with lots of images, using container-fluid and scrset beyond 1200px. Smallest is on a iPhone 5 with 320px wide and the largest for a screen of 2400px. So we need to have the images available without rescanning.
Yes he doesn’t need both xs and sm thumbnail types since they are the same size, that just creates more files on the server for no reason.
But no the created thumbnail image for sm doesn’t have to be 720px
He might simply have decided he wants to keep the same size of 540px from 0 to 577px and also from 578 to 767px. So if that’s the case, he doesn’t need the line 'sm' => '576px',
What I’m trying to say is that your assessment is logical from a usability standpoint, it’s what makes sense.
But from a coding perspective, the code in Aflixia’s is not wrong.