• Resolved timholz

    (@timholz)


    Hi
    In my settings i have the following breakpoints:
    1024,640,480,320

    After several tests on gtmetrix, ios Simulator, chrome emulator the only breakpoints that are take in account are 1024 and 640.
    Why are 480 and 320 not coming into play?

    regards
    theo

    p.s.:thanks for the plugin

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Takis Bouyouris

    (@nevma)

    Hi there,

    I will do my best to help!

    Well, these sizes will be created and used when they are accessed by a device of that particular size. Did you test it with such a device?

    But there is a little “catch”. We take into account the biggest dimension of the device not just its width. The reason is that we would not want to create too many image sizes for each device and we do not want to switch for portrait and landscape orientations. We need “mean” values. Actually, we have found that about 2-3 sizes are more than enough to give you great image size reduction for almost all devices today.

    By the way, did you send another message previously. I got a notification, but I cannot find the message now. 🙁

    Thread Starter timholz

    (@timholz)

    Hi Nevma
    Thanks for your care. Yes, i previously sent a message, but then edited it, for some questions were resolved in the mean time.
    Yes, i tested with various simulations like ios simulator, browserstack and google chrome emulator. Some pictures are taken in account, others are completely ignored.
    For instance i made a test on gtmetrix, in chrome android device mode.
    The picture has originally 511 square pixels. Apparently this device does not find an adaptive image, for the 511 pixels are scaled down to 284pixels. That is a lot.
    So, i resume, that the breakpoints are in portrait mode the height of the device in css pixels.
    regards
    theo

    Plugin Author Takis Bouyouris

    (@nevma)

    Hi,

    Yes, for instance in iPhone3, where the dimensions are 320px width and 480px height, then the biggest of (320, 480) will be taken into account. If you check at a website like http://mydevice.io/devices/ you will find that there are so many different widths and height that it would make no sense to target them all!

    So we propose to target the most important screen sizes and take the biggest dimension into account.

    I am not sure I understood your example of the 511px image! 🙁

    What are your thoughts? Does the plugin work not as expected? Should the logic be different in some way? I appreciate honest ideas? 🙂

    Thread Starter timholz

    (@timholz)

    Hi Nevma

    Thanks a lot for your response.

    Yes it works as expected and it does a good job in optimizing images for different devices.
    I was just assuming that it had more impact.
    For instance this image i mentioned has 511spuare px. But since many mobile devices are about 640px high, there is no adaption for this image.
    If the screen width would be the relevant then the image would also resize.
    My idea is that it would be convenient if the plugin would offer to choose between portrait and landscape adaption.

    And i have observed another issue.
    I have tested two sites with image sliders.
    On one side i have a small slider, and all the pictures are resized. That’s absolutely fabulous.
    On the other i have a fullscreen image slider. Here only the first two images are resized. Every third is ignored.
    Do you have any idea why this is happening?

    All the best to you and your interesting work.

    regards
    Theodor Imholz

    Plugin Author Takis Bouyouris

    (@nevma)

    Well, perhaps the 511px is too small already to be resized!

    But perhaps this could be a new setting we could add to the settings page. However, how would we treat the case when the device changes its orientation? The image would be already loaded and now its size would be perhaps small for the new orientation. This is something I do not have a stable solution in mind yet…

    (I will answer to your other question in your other support thread.)

    Plugin Author Takis Bouyouris

    (@nevma)

    Hi! Is the issue in here resolved, so I can mark the thread as resolved, too?

    Thread Starter timholz

    (@timholz)

    Hi Nevma
    Yes, of course, the topic is resolved.
    regards
    theo

    Plugin Author Takis Bouyouris

    (@nevma)

    Thank you, my friend!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘how does it actually work?’ is closed to new replies.