qa-detect-mobile-keyboard

Detecting wrong mobile keyboards involves probing the input type and inputmode attributes against the field's label or placeholder. This catches mismatches where text, email, search, or numeric inputs trigger the wrong soft-keyboard layout.

Inputs are obscured when focusing them pushes the field into the lower viewport area or under a fixed bottom bar. Keyboard occlusion checks focus the lowest visible input to verify if the on-screen keyboard covers the active form element.

You test responsive checkout flows by running in-page probes on input attributes, focus behavior, and viewport position. This mobile usability review catches wrong keyboard triggers and layout occlusion that hurt form completion rates on small screens.

Yes, this detection works with Playwright for responsive pages by probing labels, input type, inputmode attributes, and focus behavior. It checks for fixed bottom-bar overlap and viewport position changes when the on-screen keyboard appears.

A numeric field shows a text keyboard when the input type and inputmode attributes are not properly configured for numeric input. Detecting this requires comparing the field's label or placeholder against its actual type and inputmode properties.