passij

@emermatomo, thanks again for the 404 hint! I enabled and disabled a few setting in the Matomo wordpress settings, I also enabled shortly the tracking-debug-mode and out of a sudden, the 404 is gone and tracking seems to work. I don’t know what happend, but no matter 😉

Thanks @emermatomo!

This is the output of the debug.log

[31-Jul-2023 07:45:52 UTC] Matomo: Scheduled tasks archive data

This is the URL: https://alpenluxus.com

Hi @blossomthemessupport,

thanks for your answer! It’s correct, the featured image is responsive in terms of scaling. But it does not load different sizes of images per viewport. You can achieve that with the srcset/sizes attribute.

You can check your own demo theme: https://blossomthemes.com/theme-demo/?theme=vilva

If you check the source code for the featured image, you will see just an ordinary img tag: <img src="https://blossomthemesdemo.jpg" alt="" width="900" height="500" />

Compare it with an img tag within a post and you will find the srcset attribute. The browser then decides which image to load, dependent from the viewport of the browser. This is a reduced example:
<img srcset="elva-fairy-480w.jpg 480w, elva-fairy-800w.jpg 800w" sizes="(max-width: 600px) 480px, 800px" src="elva-fairy-800w.jpg" alt="" />

https://developer.mozilla.org/en-US/docs/Learn/HTML/Multimedia_and_embedding/Responsive_images

Thank you!
Pascal

• This reply was modified 5 years, 2 months ago by passij.
• This reply was modified 5 years, 2 months ago by passij.

Thanks for your feedback! I’ll watch the conversation on Github.

I’ve figured out the same problem at the official picturefill demo sites.

Possible solution: As Safari doesn’t fully support the srcset Attribute yet, it falls back to src. So Safari always downloads the “fallback” version (in this case the full resolution image) and the appropriate image.

Any feedback is welcome!

Also I suggest to omit the fallback src attribute, as described by scott jehl http://www.filamentgroup.com/lab/to-picturefill.html