podman-desktop icon indicating copy to clipboard operation
podman-desktop copied to clipboard

Typing > (html entity) in the feedback modal causes multiple toasts

Open bobbravo2 opened this issue 1 month ago • 7 comments

Bug description

When using the feedback modal in Podman Desktop on macOS (Intel), typing the greater-than symbol (>) causes the app to unexpectedly steal keyboard focus (cursor jumps out of the text field / modal loses input), preventing further meaningful input.

Observe that when the > character is typed, focus is lost from the field / modal acts as if input field collapsed or another UI element became active.

Expected Behaviour: Typing standard characters including > should not shift focus or interrupt the text-input session; the feedback modal should remain active and accept the full message.

Operating system

macOS 25.0.0 - x64

Installation Method

Installer from website/GitHub releases

Version

~1.22.1~ (Also verified in v1.23.1)

Steps to reproduce

  1. Open Podman Desktop (version v1.23.1) on macOS.
  2. From the menu, select Help → Send Feedback (or equivalent to open the feedback-modal).
  3. Click into the “description / message” text field.
  4. Type some text, e.g., “My test > bug”.

Relevant log output


Additional context

Enabled Extensions

  • podman-desktop.compose
  • podman-desktop.docker
  • podman-desktop.kind
  • podman-desktop.kube-context
  • podman-desktop.kubectl-cli
  • podman-desktop.lima
  • podman-desktop.podman
  • podman-desktop.registries Image Image

bobbravo2 avatar Nov 22 '25 15:11 bobbravo2

Interesting enough, this conflict with the CommandPalette, we have a listener for > and F1

https://github.com/podman-desktop/podman-desktop/blob/fc07c171167cab373f6ddc9723410bfaa383719d/packages/renderer/src/lib/dialogs/CommandPalette.svelte#L168-L170

The funny things is that when you are typing > this trigger the listener

This is kinda funny, as this is easily triggered anywhere in the application, for example from any search bar typing > will open the command palette

https://github.com/user-attachments/assets/4bb313a0-ea36-4d76-a424-a6b1a11b7949

cc @gastoner @benoitf

axel7083 avatar Dec 02 '25 16:12 axel7083

usually in other places, we check that the component is opened or not before handling the key

so F1 is the trigger to open the component (need to listen globally) but the other keys should be monitored only if command palette is displayed

benoitf avatar Dec 02 '25 16:12 benoitf

https://github.com/podman-desktop/podman-desktop/blob/8910b7a902c707e3b221f0c554a8e36c152a3493/packages/renderer/src/lib/dialogs/QuickPickInput.svelte#L244-L247

benoitf avatar Dec 02 '25 17:12 benoitf

I think we have added the shortcuts to command pallete so you can e.g. type > if you want to just run some commands and not have press F1 and then > to move to commands cc @vancura @MariaLeonova WDYT?

gastoner avatar Dec 02 '25 18:12 gastoner

IMHO, > can't be a global shortcut, you can enter this character on so many things

benoitf avatar Dec 02 '25 18:12 benoitf

@benoitf I agree, that seems to be too easily accessible, the > should work only once the search/command palette is already open; otherwise it steals focus too easily. See, for example, Cursor.

MariaLeonova avatar Dec 03 '25 08:12 MariaLeonova

That's true. Do we have a better global keyboard shortcut? I don't know, frankly. If there's nothing better, it should be removed.

vancura avatar Dec 03 '25 08:12 vancura