Files
KoalaSync/tests/e2e/fixtures/pages/reloading-frame.html
T
KoalaDev ef1fdc89c3 test: prove the frame lifecycle fixes against the real extension
The evidence for the frame-observation fixes was a reimplementation of the
logic measured in a browser console, not the shipped code. Two extension
specs now cover the observable behaviour end to end: a player frame that
swaps its document, and the same one level deeper.

The nested case fails against the pre-fix content.js and passes now. The
top-level case already passed before the fix, so that fix removed dead
observer registrations without changing what a user could see; recorded
here so the distinction is not lost.

Also adds bench-finder.mjs, which measures the extracted shipped finder
instead of a transcription of it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-14 07:53:45 +02:00

10 lines
505 B
HTML

<!doctype html>
<meta charset="utf-8">
<title>Reloading player frame</title>
<h1>Player frame that swaps its document, like a server or quality switch</h1>
<!-- Nothing in the top document changes when the frame navigates, so the top
document's MutationObserver never fires. Only a load hook on the frame can
notice, which is exactly what this fixture pins down. -->
<iframe class="player_frame" width="860" height="490" src="frames/player-frame.html"></iframe>
<script src="ready.js"></script>