Quick answer: Construct 3 Text Input with focus disabled still capturing keystrokes? Browser fires keydown on disabled fields too - prevent default in your handler or test focus before action.
Disabled inventory search field consumes the Enter key, blocking the menu confirm action.
Check focus before action
'Is element focused' before triggering keyboard actions. Disabled fields fail the check.
preventDefault on disabled
Custom JS: on keydown for disabled field, preventDefault. Stops the event from propagating.
Or use display:none
Truly invisible field. Doesn't capture events. Useful when disabled-but-visible isn't required.
“Disabled means cosmetic, not gone. Event flow ignores the flag.”
Standardize how you hide vs disable inputs. Hide for unavailable; disable for not-yet-fillable. Different semantics; different bugs.