Server-backed download fixtures
These fixtures cover attachment headers, slow streams, duplicate filenames, and extension edge cases without relying on third-party sites.
Attachment
Plain attachment with a standard filename.
Inline content
Inline text payload with no forced attachment.
Unicode filename
Attachment whose filename uses non-ASCII characters.
RFC 5987 filename*
Attachment that exercises filename* parsing.
Missing filename
Attachment with no Content-Disposition filename.
Slow stream
Streamed response that arrives in chunks to exercise progress UI.
Risky extension fixture
Harmless text payload named like a risky executable/script extension.
Client-side downloads
Blob and data URL downloads often bypass different code paths than server attachments, so they are useful for comparison.
Context-menu save fixtures
Use the browser context menu on these fixtures to test save-image or save-audio paths that route through native browser UI.
Image fixture
Audio fixture
Manual checklist
- Trigger the burst test once with permission already granted and once from a clean browser profile.
- Download the same fixture repeatedly to inspect duplicate filename behavior.
- Use the context menu on the image and audio fixtures to compare save-media prompts to ordinary downloads.