progressive images lazy load #30

New issue

Open

opened 2025-09-10 12:56:01 -06:00 by rs-pencil · 0 comments

rs-pencil commented

2025-09-10 12:56:01 -06:00

(Migrated from spacecruft.org)

They get a red box around them, maybe just in FF. clicking on them is fine.

opus says

Diagnosis Confirmed: Progressive JPEG + Lazy Loading Issue in Firefox
The Problem:

NY Post serves all their images as progressive JPEGs (as opposed to baseline JPEGs)
Firefox has a known issue with progressive JPEGs when combined with loading="lazy"
This causes the images to show as broken (red dotted boxes) initially
When clicked, the browser forces a full load, which then works
Evidence:

All NY Post images (article_6xxx) are progressive JPEGs
Other sources' images are baseline JPEGs and work fine
The issue occurs on NY Post's own website (they likely use lazy loading too)
The issue is Firefox-specific
The Fix:
We need to remove loading="lazy" specifically for progressive JPEG images from NY Post. Since we can't detect if an image is progressive on the client side, we should remove lazy loading for all NY Post articles.

They get a red box around them, maybe just in FF. clicking on them is fine. opus says Diagnosis Confirmed: Progressive JPEG + Lazy Loading Issue in Firefox The Problem: NY Post serves all their images as progressive JPEGs (as opposed to baseline JPEGs) Firefox has a known issue with progressive JPEGs when combined with loading="lazy" This causes the images to show as broken (red dotted boxes) initially When clicked, the browser forces a full load, which then works Evidence: All NY Post images (article_6xxx) are progressive JPEGs Other sources' images are baseline JPEGs and work fine The issue occurs on NY Post's own website (they likely use lazy loading too) The issue is Firefox-specific The Fix: We need to remove loading="lazy" specifically for progressive JPEG images from NY Post. Since we can't detect if an image is progressive on the client side, we should remove lazy loading for all NY Post articles.