Change Details

Since we started lazy loading images on the mobile website, we are no longer restricting images to 100% of the viewport. This is because lazy loaded images are one level 'deeper' and thus the direct child selector of ```lang=css .content a > img { max-width: 100% !important; height: auto !important } ``` no longer matches. {F5222040} {F5222042}

Since we started lazy loading images on the mobile website, we are no longer restricting all images to 100% of the viewport. This is because lazy loaded images are one level 'deeper' and thus the direct child selector of ```lang=css .content a > img { max-width: 100% !important; height: auto !important } ``` no longer matches. To take an example go to Russia#Get in on Wikivoyage: https://en.m.wikivoyage.org/wiki/Russia On a mobile screen (e.g. iPhone) the lazy loaded image placeholder and the loaded image force themselves out of the viewport. {F5222040} {F5222042}

Since we started lazy loading images on the mobile website, we are no longer restricting all images to 100% of the viewport. This is because lazy loaded images are one level 'deeper' and thus the direct child selector of ```lang=css .content a > img { max-width: 100% !important; height: auto !important } ``` no longer matches. To take an example go to Russia#Get in on Wikivoyage: https://en.m.wikivoyage.org/wiki/Russia On a mobile screen (e.g. iPhone) the lazy loaded image placeholder and the loaded image force themselves out of the viewport. {F5222040} {F5222042}