[GUI] Meet the 44px touch-target minimum for Initializers controls

[romanlutz]

Important

Maintainer-owned: This issue is intentionally labeled not ready yet. Please leave implementation to a PyRIT maintainer unless a maintainer explicitly assigns or approves the work.

Describe the bug

At a 390×844 mobile viewport with touch/coarse-pointer input, three primary Initializers controls have 32px clickable heights: Refresh, the additional-initializer selector, and Add initializer.

These controls fall below the application's 44px coarse-pointer target convention and are materially harder to activate accurately on touch devices, especially because the selector and Add button sit directly beside and below one another. Severity: low; the controls remain usable, but mobile interaction is less forgiving than the rest of the touch-optimized interface.

Steps/Code to Reproduce

1. Emulate a 390×844 mobile viewport with touch input and a coarse primary pointer.
2. Open the Initializers page.
3. Measure the clickable bounding boxes of the visible controls.
4. Observe these dimensions:
   • Refresh: 96×32 CSS pixels
   • Additional-initializer selector: 220×32 CSS pixels
   • Add initializer: approximately 140×32 CSS pixels
5. Compare with the 44px minimum used for coarse-pointer controls elsewhere in the frontend.

# N/A - GUI-only reproduction; no Python code is required.

Expected Results

Primary controls on the mobile/coarse-pointer layout should provide at least a 44px clickable height without introducing horizontal overflow or disrupting the responsive stacking order.

Actual Results

All three controls measure 32px high. The page otherwise reflows without horizontal overflow, so the issue is limited to touch-target sizing rather than general responsive layout failure.

Screenshots

A sanitized annotated mobile screenshot and focused WebM recording are attached in the evidence comment below. The capture contains only the application viewport and measured dimensions.

Versions

• PyRIT commit: 3dd9946ee4ef08a2048c64ff4b29d3a856a8068e
• OS: Windows_NT
• Browser automation: Playwright Chromium (@playwright/test 1.62.0)
• Viewport/input: 390×844, touch enabled, coarse pointer
• pyrit.show_versions(): N/A for this frontend-only reproduction

[romanlutz]

Sanitized evidence

The annotations show the measured clickable bounds at a 390×844 touch viewport: Refresh 96×32, selector 220×32, and Add initializer approximately 140×32 CSS pixels.

Watch the focused 5-second mobile WebM recording

Safety: the recording contains only the local application viewport and measured dimensions. No credentials, provider data, browser chrome, filesystem paths, or backend traceback are present.

[github-actions]

Thanks for the bug report! A maintainer will triage shortly. If you can add a minimal reproduction, screenshots, or your PyRIT/OS version (you can edit this issue), that would help us investigate.