Problem
src/components/ui/ToastContainer.vue uses z-[200]. DaisyUI v5 .modal is z-index: 999, and our teleported modals (ConfirmDialog, DeleteNodeModal) are z-[1000]. So when a modal is open, toasts render behind it.
This matters for the new Proxmox action flow: useProxmoxTasks fires error/success toasts (e.g. "Stop the VM first", protected-VMID errors) while the ConfigPanel / DeleteNodeModal may still be open — the user can miss them.
Fix
Raise ToastContainer above the modal layer (e.g. z-[1100]) so toasts are always visible. Confirm it doesn't obscure anything that should sit above toasts.
Reference
Surfaced during the 2026-06-09 modal z-index fix (fix(canvas): raise DeleteNodeModal/ConfirmDialog above DaisyUI modal z-index). Left as a separate, intentional decision at the time.
Problem
src/components/ui/ToastContainer.vueusesz-[200]. DaisyUI v5.modalisz-index: 999, and our teleported modals (ConfirmDialog,DeleteNodeModal) arez-[1000]. So when a modal is open, toasts render behind it.This matters for the new Proxmox action flow:
useProxmoxTasksfires error/success toasts (e.g. "Stop the VM first", protected-VMID errors) while the ConfigPanel / DeleteNodeModal may still be open — the user can miss them.Fix
Raise
ToastContainerabove the modal layer (e.g.z-[1100]) so toasts are always visible. Confirm it doesn't obscure anything that should sit above toasts.Reference
Surfaced during the 2026-06-09 modal z-index fix (
fix(canvas): raise DeleteNodeModal/ConfirmDialog above DaisyUI modal z-index). Left as a separate, intentional decision at the time.