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
Commit 5e5bd4a
Browse filesBrowse the repository at this point in the historyBrowse files
The >50 mounted [data-message-id] readiness wait baked in an
un-virtualized-DOM assumption: it only passes when the impl mounts every
visible-band row at once, so a real virtualizer (which windows the mount
set below 50 by design) times out and never yields a number — the exact
impl-coupling this fixture's rekey exists to remove. Replace it with the
signal any timeline exposes once loaded: the scroll container overflows
its client box by a wide multiple (corpus ingested, whether it mounts 12
rows or 500) AND >=1 message row present (sampler needs a live anchor).
Zero per-impl branches.
Add the post-momentum-bite-set restricted max-px print (Dawn's co-gate):
the discriminator is bite count AND bite max-px both down, not count
alone — a candidate could drop count while leaving survivors larger
(fewer, more violent snaps). Global max spans all reversals; this is the
max snap within the bite set the discriminator counts.
Both engines reproduce the survivor class on the patched fixture:
chromium 22 reversals / all tracking-failure / aboveΔ=0 / 21 still-frame
/ bite 21 @ 60px; webkit 19 / all tracking-failure / aboveΔ=0 / 19
still-frame / bite 19 @ 60px.
Co-authored-by: Tyler Longwell <[email protected]>
Signed-off-by: Tyler Longwell <[email protected]>
0 commit comments