Intro to x86 Assembly with FASM

revolution wrote:

I wonder if it is possible to turn off that behaviour?

revolution it is possible indeed.
The issue: some wordpress templates are prepared to serve images depending on your screen pixel ratio. In the sense of if you have a device with pixel ratio 2:1 it will show you a bigger image so that it looks smoother.

In the case of wordpress it is done with wp_get_attachment_image(). This will generate the img tag with blank image and data-src with different images. Later on some javascript will set the src attribute of the image to something "suitable" for your device.
But if you use something like this you assure that there would be an image set.

Quote:

<img src="<?=wp_get_attachment_image_src( int $attachment_id, string|array $size = 'thumbnail');?>" class="" alt="">

The script should set a default image and then later on switch it to something else. Then again, probably it was done to save bandwidth. Then once more again... it is silly that a bloated javascript tries to preserve bandwidth.

It is as risky as having a dynamic webpage depending on a database. Condompress is updated regulary to patch all the vulnerabilities and making the browsing a safe experience for everybody.

Best regards
^^

Edit, just for the curious once, here is the javascript responsable for the update
it takes as a parameter the img node and then changes

Code:

function updateImage( imageNode, imageData ) {
        /**
         * bla bla bla bla bla.....................
         */
         srcset = $imageNode.attr( 'srcset' );
         src = $imageNode.attr( 'src' );

        // Remove srcset and sizes if the image file was edited or the image was replaced.
        if ( srcset && src ) {
                src = src.replace( /[?#].*/, '' );

                if ( srcset.indexOf( src ) === -1 ) {
                        $imageNode.attr( 'srcset', null ).attr( 'sizes', null );
                }
        }

        /**
         * bla bla bla bla bla.....................
         */
}