You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Trace: store page resources and replay from the archive #499
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.
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.
Activity
vishnuv688 commentedon Oct 30, 2026
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.
vishnuv688 commentedon Nov 4, 2026
Implemented in #533. It closes this issue when merged.
Store page stylesheets and fonts in the trace and replay them from it