#10257 Confirmation dialogue button alignment

[andrewvarga]

Fixes #10257 and a few related issues.

DeleteProjectDialog.tsx previously:

Now (on Windows the order is: Delete, Cancel but they are still both aligned to the right):

SetVarNameModal.tsx previously:

Now:

ToastUpdate.tsx previously:

Now:

• Removed UpdatedRestartModal.tsx because it wasn't used anywhere, I think this was replaced by ToastUpdate.tsx
• Fixed a React warning in DeleteProjectDialog.tsx:

ProjectCard.tsx:219 In HTML, <p> cannot be a descendant of <p>.
This will cause a hydration error.
  ...
    <j3 target={{current:null}}>
      <l6 force={false}>
        <z initialFocus={undefined} containers={function} features={22}>
          <l4>
          <div onKeyDown={function onKeyDown} onBlur={function onBlur} ref={function}>
            <div className="relative z-50" id="headlessui..." role="dialog" aria-modal={true} aria-labelledby={null} ...>

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
modeling-app	Ready	Preview, Comment	Mar 9, 2026 0:31am

[graphite-app]

The custom Escape key handler is redundant and potentially problematic. The @headlessui/react Dialog component already handles Escape key presses via the onClose prop (line 61). This custom useEffect hook adds a window-level listener that will also call onDismiss() when Escape is pressed, potentially causing onDismiss to be invoked twice.

The event.stopPropagation() may not prevent the Dialog's internal handler from firing since they operate at different levels.

Fix: Remove this entire useEffect block. The Dialog's built-in Escape handling is sufficient:

// Remove lines 19-32
// The Dialog component's onClose={onDismiss} already handles Escape

Spotted by Graphite



Is this helpful? React 👍 or 👎 to let us know.

[jtran]

Code looks good to me, and I tested the delete project. I don't know if the graphite comment is right, though.

[andrewvarga]

Code looks good to me, and I tested the delete project. I don't know if the graphite comment is right, though.

Yeah, I tried with the Dialog's onClose first but that never triggered because we're capturing key presses in other places too..