Skip to content

V0.3.4 · Landing image loading

Latest

Choose a tag to compare

@inksong inksong released this 26 Oct 07:53
· 41 commits to main since this release

V0.3.4 · Landing image loading

V0.3.4 is a patch release of V0.3.3.

Fix

Since V0.3.3 the Event Lab section follows the first screen of the landing page. Chrome starts native lazy images 1250 to 2500 px ahead of the viewport, so the section's images (about 1 MB: the lead image, four camera frames and seven sample thumbnails) loaded together with the page. On the outbound link of the public host (about 3 Mbps, measured on 2026-10-25 from Ningbo and from the United States over the public internet) they delayed the application chunks that "Open my sandbox" loads right after, and the start sheet took more than 5 s to appear. Landing images now get their address only when they come within 200 px of the viewport.

Verification

  • D3 regression gate, light tier, on the release tree: contracts, web unit tests, lint, the public build, the K9 checks and the lab build passed. Version-pinned Python tests pass.
  • Public end-to-end tests against https://anet4d.agentnetwork.org.cn, including /lab/ and the case "landing to an own sandbox in two clicks", passed 7 of 7. The /lab/ publishing checks passed, except the connection check, which has no file of 12 MiB or more to test (known item F-131).
  • On a local build, the landing page requests no Event Lab image before the visitor scrolls, and all of them load once the section comes into view (desktop 1440 x 900 and phone 390 x 844).