File the empirical bug, not the code-trace

When a user reports a keyboard handler not firing but the source clearly attaches a window-level listener that should handle it, do not get sucked into a long live-debugging session before filing. Write the issue around the user observation, point at the suspect handler location, and explicitly call out the likely confounders (child component stopPropagation, form-level listener, focus trap). The maintainer will reproduce with devtools in seconds; you would burn ten minutes guessing.