Skip to content

Trace: store page resources and replay from the archive #499

Closed

Description

@vishnuv688

Part of #494.

Problem

The player replays a page from its captured DOM but loads that page's stylesheets, fonts and images from the live site under test. As a result:

  • Cross-origin fonts fail unless the site sends CORS headers. On the-internet the Login button's Font Awesome icon renders as an empty box, in show-trace and in the hosted player alike.
  • From an https page, such as the hosted player, the browser blocks http resources, so a trace of an http site renders unstyled.
  • A trace replays wrongly once the site changes or goes away, and not at all for an internal site the viewer cannot reach.
  • Opening a trace makes requests to the tested site.

Proposal

Capture the resources the page actually used (stylesheets, fonts, images) into the trace, content-addressed by sha1, and serve them from the archive during replay. This is a capture change in all four adapters plus a replay change in the player.

Size matters here (see the trace size budget sub-issue): store each resource once, only what the page used, skip analytics and media, cap the size per resource, and avoid repeating the same site assets in every per-test zip.

Activity

  1. self-assigned this
    on Oct 29, 2026
  2. vishnuv688 commented on Oct 30, 2026

    @vishnuv688
    MemberAuthor

    Decision: store stylesheets and fonts by default, each once per trace by content hash; images stay on the live site unless an option enables them. Size is held by the #496 budgets.

  3. vishnuv688 commented on Nov 4, 2026

    @vishnuv688
    MemberAuthor

    Implemented in #533. It closes this issue when merged.

  4. added a commit that references this issue on Nov 9, 2026
    671aa04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions