[thavguard]

Removing a <tr> during its entry animation throws when its positioned ancestor has no cached coordinates. WebKit explicitly resets position: relative to static on table row groups (engine source), so AutoAnimate can walk past the observed tbody to an unobserved wrapper.

Fall back to measuring that ancestor when its cache entry is missing. The production change is one line.

Fixes #248.

The regression test uses a plain HTML table, default options and unchanged styles. It verifies that a row removed during entry is cleaned up without an exception and its sibling survives. Run it in Chromium and WebKit:

export PATH="$PWD/node_modules/.bin:$PATH"
pnpm exec playwright test tests/e2e/removal-position.spec.ts --workers=1 --project=chromium --project=webkit --retries=0

Focused CI: unpatched core — Chromium passes, WebKit fails with parentCoords.top; patched core — both pass. The same minimal test is used in both runs.

[vercel]

@thavguard is attempting to deploy a commit to the Formkit Team on Vercel.

A member of the Team first needs to authorize it.

[justin-schroeder]

Merged 🎉 Thanks! Ships in @formkit/auto-animate@0.10.1 — I'll ping here when it's on npm.