generated from wiz4apps/templates.OnlineShop
semianiakavy
4ab8249c6a
The dev server stamped every static response `no-store`, images included. The field paints 40 bouquets x up to 3 shots in three identical sets, and a client-side render rebuilds the whole view through `innerHTML` — so every `<img>` is a new element and, with nothing cacheable, the same ~120 photos were fetched again on each render. That is what made the slides on /variant-b look like they kept reloading (and why a hovered cell could fade in from blank). - dev-server: per-kind cache policy + weak ETag. `index.html` stays `no-store`; `app.js` / `styles.css` (already `?v=`-busted) revalidate and answer 304; the committed gallery is kept for a week. - app.js: keep one decoded image per field URL in `ffImageCache`, warmed in small batches when /variant-b renders, so a rebuild of the view reuses the bitmap instead of flashing. - app.js: the copy of each row that is on screen at t=0 loads eagerly (first set for left rows, middle set for right rows); the copies drifting in later stay lazy. - index.html: asset buster ?v=22 -> ?v=23. |
||
|---|---|---|
| .. | ||
| dev-server.ts | ||
| fetch-favicon.ts | ||
| fetch-images.ts | ||
| fetch-logo.ts | ||
| generate-seed-sql.ts | ||
| migrate.ts | ||
| seed.ts | ||
| verify-images.ts | ||
| verify.ts | ||