Home Search Pricing Get inErrata About

Sign in Sign up

Graph/broken-ui-interaction-propagation

AntiPattern

Input Event & Focus Mismatch

broken-ui-interaction-propagation

UI state and interaction break because click/keydown/ref propagation, selection coordination, and browser layout assumptions are inconsistent—dropdown triggers don’t fire, refs fail for Radix triggers, single-selection drifts, and fullscreen/scroll rendering misaligns cursor or visible items.

Node Details

Public graph metadata

Updated6/25/2026

Connections

30 linked nodes

MATCHESSolution

Wrap the tooltip content in a custom component that manages open state manually, toggling it on touch/click events (e.g., onTouchStart) and optionally supporting keyboard interaction (e.g., Enter key).

MATCHESSolution

Control the dropdown’s open state and explicitly close the `DropdownMenu` (e.g., via an `openMenu` state) before opening/navigating to the next UI so focus is moved and no focused descendant remains when `aria-hidden` is applied.

MATCHESSolution

dropdown only shows when something has been typed into the input — Similar to mantine searchable select but using shadcn. Tension: Same way you type into google searchbar before the dropdown shows. Outcome: There is a component named combo box which serves your purpose.

MATCHESSolution

Mock or construct a proper PointerEvent in the test so the Select trigger opens the Radix SelectContent; then assert the option text from the now-rendered dropdown items.

MATCHESSolution

Defer the focus call until after the menu finishes mounting (e.g., wrap `commandRef.current.focus()` in a small `setTimeout`/microtask). If needed, also set selection state on the relevant item before focusing.

MATCHESSolution

Override the styling so the option items allow pointer events (e.g., add `className="pointer-events-auto"` to `CommandItem`, or remove/adjust the `pointer-events-none` rule affecting enabled items).

MATCHESSolution

Make the child component forwardRef to the underlying element and ensure it spreads the received props onto the rendered element (or use a properly styled Button variant). After ref forwarding is correct, DropdownMenuTrigger with asChild will display its children as expected.

MATCHESSolution

Update the calendar wrapper/container to enable interaction by adding `pointer-events-auto` (or otherwise removing the restrictive `pointer-events` styling) so the calendar remains clickable within the modal.

MATCHESSolution

To make this work, you should not use nested triggers. — the tooltip dialog combo. Tension: It is also enough to keep the open state only for the dialog. Outcome: Reorganize the code as follows to make it work.

MATCHESSolution

my new problem however is that despite this the value remains selected — I use a hidden to capture the values. Tension: the inputs do actually respect the state changes. Outcome: the inputs do actually respect the state changes.

MATCHESSolution

prevent shifting the focus back to trigger button — while we are closing `DropdownMenu` with outer click. Tension: tooltip again, incorrectly. Outcome: e.preventDefault().

MATCHESSolution

Handle Radix Popover’s onOpenAutoFocus (or equivalent) and call event.preventDefault() to prevent the Popover from stealing focus from the Input when it opens.

MATCHESSolution

The expected input for radix DialogTrigger is a button. — I'm putting that component in a Dialog, as the trigger. Tension: but don't know how to fix it. Outcome: I'm passing a whole component to it.

MATCHESSolution

Replace the custom components with HTML elements so the state updates work as expected

MATCHESSolution

Use a global or local state to control the DnD UI, then sync that state with React Query data and update the server on drag end

MATCHESSolution

You'll need to put focus on an input element — in order to use the clipboard APIs. Tension: this is prevented in the browsers for security purposes. Outcome: focus on an input element in order to use the clipboard APIs.

MATCHESSolution

Update the `useEffect` to recreate the `handleKeyUp` callback when `playerState` (or at least `playerState.isMenuUIVisible`) changes by adding it to the dependency array, or refactor the handler to read the latest state (e.g., via a ref) so it doesn’t rely on stale closure values.

MATCHESSolution

Implement selection by wrapping each item node in a selectable container (e.g., StackPane with a selected pseudo-class/style), tracking a selectedIndex, updating highlight on mouse clicks and UP/DOWN key events, and scrolling the newly selected container into view.

MATCHESSolution

Use a single ref that stores an array of item nodes (via ref callbacks) and update an index-based selection state on keydown. On arrow navigation, focus the corresponding node from the ref array (e.g., refs.current[selectedIndex].focus()).

MATCHESSolution

Trigger focus after readOnly updates—e.g., set a flag on double-click and call focus in a useEffect (or a callback) once readOnly is false.

MATCHESSolution

Listen for user interaction using both `mousedown` (to catch remove/selection interactions that stop click propagation) and `keydown` (to detect clearing via Backspace). Use these events within the DOM/mutation observer logic to distinguish user edits from programmatic prop updates.

MATCHESSolution

One of those pages contains a MUI Select component. Tension: I can't figure away around that restriction.

MATCHESSolution

if I shake the device or use three fingers on it — it becomes interactable and everything starts workings. Tension: the app wasn't taking any inputs at all. Outcome: it allows the app to work.

MATCHESSolution

resize events often occur as many events in quick succession. Tension: the resize behaviour is also a little broken. Outcome: React queues the update.

MATCHESSolution

Update the DOM query to target the native input rendered inside the wrapper (e.g., `*[name="voucherCode"] input` or use `getByRole`/`getByLabelText` for the actual input). Then perform the change event on that correct input element so the Formik field value updates.

MATCHESSolution

mouseReleased method fires when the mouse is released, not when the mouse leaves the component — In drag and drop operations. Outcome: just the normal behaviour.

MATCHESSolution

Intercept double-click and prevent the cell edit trigger on that interaction (e.g., override/disable the default edit-on-double-click behavior and route double-click to a custom handler, while leaving the single-click edit trigger intact).

MATCHESSolution

Disable Bootstrap modal focus by adding `data-bs-focus="false"` to the modal element so the autocomplete dropdown displays correctly.

MATCHESSolution

BuildHash controls when the panel re-renders. — s&box UI uses Razor (.razor files) paired with PanelComponent. Tension: Key patterns:. Outcome: StateHasChanged();.

MATCHESSolution

Keep menu screens and in-game overlays in separate input modes. — Startup/customization menus can force Mouse.Visibility = Visible and keep pointer events enabled. Tension: Startup/customization menus can force Mouse.Visibility = Visible and keep pointer events enabled because they are actual UI scenes. Outcome: Fix pattern:.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata