26 lines
1.1 KiB
Markdown
26 lines
1.1 KiB
Markdown
# WRNexusJS v0.6.0 R9 — ToggleCount animation stability
|
|
|
|
R9 fixes the final full-suite failure in `ToggleCount`.
|
|
|
|
## Root cause
|
|
|
|
The previous animation scheduled the next frame only after the preceding timeout fired. Under a heavily loaded full test suite, timer drift accumulated across every frame and the animation could finish later than `animationDuration`.
|
|
|
|
## Fix
|
|
|
|
- Every animation frame is scheduled immediately against its absolute offset within `animationDuration`.
|
|
- The displayed value remains at the previous value synchronously after a toggle.
|
|
- Every intermediate value is rounded to an integer.
|
|
- The final value is independently scheduled at exactly `animationDuration`.
|
|
- Animation tokens prevent stale timers from an earlier toggle overwriting a newer selection.
|
|
- Browser modules now bind peer client/shared functions through `context.functions`, so generated functions can safely call one another.
|
|
- `animateValueAt` is classified as a client function because it touches DOM nodes and schedules browser timers.
|
|
|
|
## Local validation
|
|
|
|
```powershell
|
|
bun install
|
|
bun run validate:0.6
|
|
bun run check
|
|
```
|