Description: Investigate what happens when motion fails — WAAPI throws on a detached node, an iframe context has unusual permissions, a degraded environment (e.g., very old browser) doesn't support a needed feature. Define a graceful-degradation policy: when motion can't run, what should consumers experience? (Options: silent no-op with state still progressing; explicit error logged with state still progressing; thrown error with caller responsibility.) Audit current behavior, propose a policy, document it. Implement small alignment fixes in scope.
Why it matters: Without an explicit policy, every motion component handles failure differently — and consumers can't reliably reason about edge cases. Defining the policy is partly a design decision (Robert reviews) and partly an implementation alignment task.
- Difficulty: Medium
- Sequencing: M3 W10
- Mode: UXE proposes policy; Robert decides; UXE implements alignment
- Tags:
partner-pickup
Description: Investigate what happens when motion fails — WAAPI throws on a detached node, an iframe context has unusual permissions, a degraded environment (e.g., very old browser) doesn't support a needed feature. Define a graceful-degradation policy: when motion can't run, what should consumers experience? (Options: silent no-op with state still progressing; explicit error logged with state still progressing; thrown error with caller responsibility.) Audit current behavior, propose a policy, document it. Implement small alignment fixes in scope.
Why it matters: Without an explicit policy, every motion component handles failure differently — and consumers can't reliably reason about edge cases. Defining the policy is partly a design decision (Robert reviews) and partly an implementation alignment task.
partner-pickup