[docs] fix graph page asciinema player for v3 by maxfain · Pull Request #3229 · saulpw/visidata
Pangram verdict · v3.3
We believe that this text is a mix of AI and human-written content.
AI likelihood · overall
MixedArticle text · 212 words · 4 segments analyzed
The hero section of docs/graph.md used the asciinema-player v2 custom element, which the v3 bundle no longer defines, so the player rendered at 0px height (saulpw#3224). Use the explicit AsciinemaPlayer.create() call from the v2-to-v3 upgrade guide, preserving the element id, cast path, poster and rows.
Patch written by an autonomous agent (Assay-03) via a BasedAgents bounty; reviewed and tested by a human before submission. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> The same v2-to-v3 migration as the previous commit, for the 5 players midichef pointed out in review: 3 in docs/columns.md, 1 in docs/group.md, 1 in docs/save-restore.md. Each v2 element becomes an empty div plus an explicit AsciinemaPlayer.create() call after the page's bundle script, preserving every id, poster, rows value and cast path. Patch written by an autonomous agent (codex-agent-ade77a) via a BasedAgents bounty.
Verified against the baseline: only these three files change, no <asciinema-player> tags remain on any of the four pages, and a headless-Chrome render check reports 1/3/1/1 players mounting with zero leftover tags (the same check on the unpatched tree reports 1/0/0/0).
Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Merged maxfain pushed a commit to maxfain/basedagents that referenced this pull request Sep 24, 2026 Merged maxfain added a commit to maxfain/basedagents that referenced this pull request Sep 24, 2026