Trigger Mouse Move

Send a target even though validation does not demand one

Mouse-move is absent from TRIGGER_REQUIRES_TARGET_KEYS, so a targetless payload passes every guard and saves cleanly. It then never fires.

bindTrigger only resolves elements when a target is present:

ContinuousTriggerStrategy.bind iterates that list, so an empty one means the mouse-move handler is never invoked. There is no fallback to the viewport, body, or document: wf:viewport binds to window only because the handler checks for that extension key explicitly.

The same dead outcome applies when a target is present but resolves to nothing, for example wf:class with an empty value.

Send {extensionKey: 'wf:viewport', value: ''} unless you specifically want to bind to elements. Nothing will tell you otherwise: the write succeeds and the interaction is silently inert.

pluginConfig persist bounds

[REJECTED] smoothness outside its millisecond range, or restingState x/y outside 0 to 100. Absent keys are legal. Guard: findMouseMoveRangeError

The panel’s Smoothness slider is 0 to 100 while the persisted bound follows the number input, so those two ranges differ. Current values are in capabilities.generated.md → Numeric bounds.

Roles

Exactly 'mouseX', 'mouseY', or 'interval'.

Accept

wf:mouse-follow — the purpose-built action

Prefer this over wf:transform x/y when the user wants an element to track the cursor. The transform form works and is what SKILL.md Example 5 shows, but it hard-codes a travel range; wf:mouse-follow handles anchoring, leave behaviour, and axis pairing for you.

One action per axis, on the matching mouseX / mouseY timeline. Never on an interval timeline.

Values are bare scalars, not [from, to] pairs — there is no from-state to express. timing is still required, as on every action.

groupId here is not timeline group routing. Two different fields share the name: timeline.groupId routes a trigger via config.assignedGroupId (see timelines-and-groups.md), while wf:mouse-follow‘s groupId pairs the X and Y actions of one follow effect.

Shapes and defaults, from MouseFollowActionConfig:

followMode is mirrored between paired actions so both sides agree; setting 'x-only' or 'y-only' on a pair tells the editor’s exit reconciler to delete the redundant sibling.

The trigger’s own pluginConfig also carries a resting state for when the pointer is idle or has left: per-axis percentages 0–100, defaulting to {x: 50, y: 50} (centre).

Interval metadata

distance and axes are authored only on an interval timeline.

Shapes:

axes is a shared shape for continuous triggers rather than a mouse-move invention — any plugin driving 2D channels uses the same object instead of re-implementing it in pluginConfig. Both fields live at timeline.triggerMetadata, beside role.

[REJECTED] Either field on a timeline whose role is not interval. The interval editor is the only place the Designer writes them. Guard: findOffIntervalMetadataError · fragment: only authored on interval mouse-move timelines

[LEGACY-OK-ON-UPDATE] An unchanged echo of a stored value on the same timeline id passes, so a duration or target read-modify-write is not forced to strip it.

[REJECTED] Interval metadata on an interaction with no wf:mouse-move trigger. Guard: findIntervalMetadataTriggerError · fragment: not write them without a "wf:mouse-move" trigger

[LEGACY-OK-ON-UPDATE] Already-stranded stored data passes: if the stored triggers also lacked mouse-move and the same timeline already carried an interval role with distance or axes, the update is not introducing the mismatch and is allowed. The panel gates its interval editor on the role alone, so a user can still edit those fields on a stranded pair.

Two writes still reject: removing the mouse-move trigger from an interaction that has interval metadata, and newly attaching those fields to an interaction that has no mouse-move trigger.

[REJECTED] A distance that is fractional, or outside 1 to 10000. Bounded in triggerMetadata‘s schema as z.number().finite().int().min(1).max(10000), so this fails schema validation before any guard runs. The bound exists to keep a malicious payload from persisting Infinity or NaN into storage; the runtime caps fires per update regardless.

Rejected

[REJECTED] A missing, duplicate, or invalid role on any timeline. Guard: findTimelineRoleError · fragment: Expected one of: mouseX, mouseY, interval

[REJECTED] Combined with any other trigger. Guard: findStandaloneTriggerError

[REJECTED] Any of control, delay, jump, speed. Guard: findUneditablePlaybackFieldError

[REJECTED] wf:viewport as a target on any trigger other than mouse-move.

[REJECTED] A wf:mouse-follow action outside a mouseX/mouseY timeline, or more than one per timeline. Guard: findMouseFollowContextError

[REJECTED] conditionalLogic — conditions are unavailable and continuous triggers are additionally excluded. Guards: findConditionsCapabilityError, findContinuousConditionsError

[REJECTED] conditionalPlayback with behavior: 'skip-to-end' while a continuous trigger is present. Use dont-animate. Guard: findConditionalPlaybackError

Panel trap

[PANEL-TRAP] timing.repeat and timing.yoyo on a continuous interaction. The panel hides both controls when a continuous trigger is present, and findScrollScrubActionTimingError keys off scrub rather than continuous, so nothing rejects them.

They are not inert. buildTweensForAction forwards a finite repeat and any yoyo straight into the GSAP tween vars, and repeat extends the timeline duration that continuous scrubbing maps gesture progress across. So a value set here changes how the interaction plays while remaining invisible and uneditable in the panel, which is the worst combination in this class.

One special case: on a percent canvas an infinite repeat: -1 is materialized to a single cycle (0), because an infinite duration would break the 0 to 1 scrub mapping. Outside a percent canvas, -1 passes through unchanged.