projectdiscovery / projectdiscovery/httpx
Headless screenshots are slow and can capture half-rendered SPAs
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10.4k
- Forks
- 1.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 13
Description
httpx downloads and launches full Chromium for headless screenshots, and captures as soon as basic load signals fire. On single-page apps that means the capture can land on the boot screen before hydration finishes, and browser startup plus the render path dominates screenshot time. A lighter browser build and stricter page-readiness gating would cut that substantially.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests. Start by locating the headless screenshot entry point, Chromium download and startup path, and current page-readiness checks; compare the existing flow on a single-page app. Done should be demonstrated by faster screenshot execution and captures that wait for the required page state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, performance, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100