mirror of
https://github.com/Shik3i/KoalaSync.git
synced 2026-08-18 15:23:13 +00:00
KoalaDev
36e1291d2c
The weighted score summed incomparable units, so size could outvote traits that disqualify an element outright. Measured on a real page: a display:none preload reports its full 1080p intrinsic size and scored 2073600, beating a visible unmuted player at 509920. Selection now compares an ordered list of signals, highest priority first: has a source, is rendered, is not a silent background loop, rendered size bucket, is playing, has controls, duration. Rendered size replaces intrinsic resolution, and mute state is gone from the ranking entirely: it is a viewer preference, not evidence about which element is the player. It stays a ranking rather than a filter, so a page of only bad candidates still yields one and findVideo never returns null where a video exists. The new tests/e2e suite runs the shipped finder against real fixture pages and drives the packed extension for injection, reinjection and remote play/pause/seek into a first-party frame. All five scoring scenarios fail against the previous implementation. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
14 lines
612 B
HTML
14 lines
612 B
HTML
<!doctype html>
|
|
<meta charset="utf-8">
|
|
<title>Background hero loop</title>
|
|
<style>
|
|
body { margin: 0 }
|
|
#hero { display: block; width: 1280px; height: 720px; object-fit: cover }
|
|
</style>
|
|
<!-- Marketing hero: large, muted, looping, no controls. Bigger than the real
|
|
player in every dimension the old scoring looked at. -->
|
|
<video id="hero" muted loop data-autoplay src="../media/loop-720p-3s.mp4"></video>
|
|
<h1>Article with an embedded player below the hero</h1>
|
|
<video id="player" data-expected width="640" height="360" controls src="../media/player-480p-12s.mp4"></video>
|
|
<script src="ready.js"></script>
|