Inconsistent feedback: native alert()/confirm() mixed with lt.toast; no in-app connection status #25

Open
opened 2026-09-08 20:57:29 -04:00 by jared · 0 comments
Owner

Overview

  • Delete worker / delete workflow / start execution failures use blocking alert() and confirm(), while schedules and prompts use lt.toast. Creating a workflow failure shows a bare "Failed to create workflow" even though the server returns a reason (e.g. webhook URL validation).
  • When the WebSocket drops, the UI silently retries every 5 s; live updates stop with no banner, and toasts for command results never arrive.
  • ESC closes .modal dialogs but not the Run Workflow parameter modal (#paramModal toggles display instead of the .show class), and no modal traps focus.

Suggested fix

Use lt.modal.confirm / lt.toast everywhere, always surface err.error, add a "⚠ disconnected – reconnecting" header indicator driven by ws.onclose/onopen, and include #paramModal in the ESC handler.

## Overview - Delete worker / delete workflow / start execution failures use blocking `alert()` and `confirm()`, while schedules and prompts use `lt.toast`. Creating a workflow failure shows a bare "Failed to create workflow" even though the server returns a reason (e.g. webhook URL validation). - When the WebSocket drops, the UI silently retries every 5 s; live updates stop with no banner, and toasts for command results never arrive. - ESC closes `.modal` dialogs but not the Run Workflow parameter modal (`#paramModal` toggles `display` instead of the `.show` class), and no modal traps focus. ## Suggested fix Use `lt.modal.confirm` / `lt.toast` everywhere, always surface `err.error`, add a "⚠ disconnected – reconnecting" header indicator driven by `ws.onclose/onopen`, and include `#paramModal` in the ESC handler.
jared added the enhancementuxfrontendpriority/medium labels 2026-09-08 20:57:29 -04:00
Sign in to join this conversation.