Skip to content

0.1.3: browser checks don't wait for photos from other sites - #3

Merged
evangress merged 1 commit into
mainfrom
browser-skip-remote-images
Nov 13, 2026
Merged

evangress merged 1 commit into
mainfrom
browser-skip-remote-images

Conversation

@evangress

Copy link
Copy Markdown
Contributor

TagKit's two --browser tests have timed out at 5 minutes since its gallery and nonprofit starter added picsum.photos photos (they took 6–11 s before). --browser waits for the page's load event, which waits for every image, so a slow image host holds each page up to 30 s in each color scheme.

  • Remote images (http:/https:) are answered with a 1×1 blank GIF. Contrast reads background colors and overflow reads layout, and an <img> with width/height keeps its size, so neither check changes.
  • New fixture and test: a photo from a host that never answers; the check finishes with no problems in under 10 s.
  • Version 0.1.3, CHANGELOG and README.

With this file dropped into TagKit's node_modules, its two browser tests pass in 6 s. Tests here: 31 passed.

After merging: cd ~/github/tagstack/tagcheck && git checkout main && git pull && npm test && npm publish, then TagKit moves to ^0.1.3.

🤖 Generated with Claude Code

Remote images get a blank stand-in. A slow image host held each page's
load for up to 30 seconds per color scheme, which pushed TagKit's
browser checks past their 5-minute limit. 0.1.3.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@evangress
evangress merged commit e887301 into main Nov 13, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant