Make Test alert play configured animations in the editor canvas #110

Closed
opened 2026-07-06 20:11:00 -05:00 by Gitchegumi · 0 comments
Gitchegumi commented 2026-07-06 20:11:00 -05:00 (Migrated from github.com)

Problem

The Alerts editor has a Test alert button, but animations do not animate inside the editor canvas when the alert is tested.

That makes the editor unreliable for its main job: letting the user build and verify an overlay without having to bounce between the dashboard and OBS every time.

Observed on the Alerts editor page:

  • Route: /dashboard/gitchegumi-gaming/alerts
  • App version shown in the UI: v0.10.4
  • Layout selected: Tips / 1920 x 1080
  • User clicks Test alert
  • Alert content/layers may appear statically, but configured animations do not play in the canvas preview.

Expected behavior

When Test alert is clicked from the editor, the canvas preview should run the same animation behavior that the runtime overlay uses.

At minimum, the canvas should preview:

  • Layer entrance animation
  • Layer active/display state
  • Layer exit animation, if configured
  • Timing/duration behavior matching the overlay runtime

Actual behavior

The alert does not animate in the editor canvas during test playback.

Acceptance criteria

  • Clicking Test alert starts an in-canvas playback cycle for the selected alert/layout.
  • Configured layer animations visibly play in the editor canvas.
  • Text/image/audio layers all continue to render correctly during preview.
  • Preview playback uses the same animation definitions as the OBS/browser-source overlay runtime.
  • Repeated test clicks reset/replay the animation cleanly instead of leaving stale animation state.
  • Playback does not dirty the editor state or overwrite layout/layer settings.

Implementation notes

This should not be a separate fake animation path if avoidable. The editor preview and browser source should share the same renderer or animation mapping so future animation fixes do not have to be implemented twice.

## Problem The Alerts editor has a `Test alert` button, but animations do not animate inside the editor canvas when the alert is tested. That makes the editor unreliable for its main job: letting the user build and verify an overlay without having to bounce between the dashboard and OBS every time. Observed on the Alerts editor page: - Route: `/dashboard/gitchegumi-gaming/alerts` - App version shown in the UI: `v0.10.4` - Layout selected: `Tips` / `1920 x 1080` - User clicks `Test alert` - Alert content/layers may appear statically, but configured animations do not play in the canvas preview. ## Expected behavior When `Test alert` is clicked from the editor, the canvas preview should run the same animation behavior that the runtime overlay uses. At minimum, the canvas should preview: - Layer entrance animation - Layer active/display state - Layer exit animation, if configured - Timing/duration behavior matching the overlay runtime ## Actual behavior The alert does not animate in the editor canvas during test playback. ## Acceptance criteria - [ ] Clicking `Test alert` starts an in-canvas playback cycle for the selected alert/layout. - [ ] Configured layer animations visibly play in the editor canvas. - [ ] Text/image/audio layers all continue to render correctly during preview. - [ ] Preview playback uses the same animation definitions as the OBS/browser-source overlay runtime. - [ ] Repeated test clicks reset/replay the animation cleanly instead of leaving stale animation state. - [ ] Playback does not dirty the editor state or overwrite layout/layer settings. ## Implementation notes This should not be a separate fake animation path if avoidable. The editor preview and browser source should share the same renderer or animation mapping so future animation fixes do not have to be implemented twice.
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
gitchegumi/GitchAlerts#110
No description provided.