Skip to content

fix: pin kiosk keyboard to viewport bottom for more search results#187

Merged
thewrz merged 1 commit intomainfrom
fix/keyboard-fixed-bottom
Feb 24, 2026
Merged

fix: pin kiosk keyboard to viewport bottom for more search results#187
thewrz merged 1 commit intomainfrom
fix/keyboard-fixed-bottom

Conversation

@thewrz
Copy link
Owner

@thewrz thewrz commented Feb 24, 2026

Summary

  • Pin the virtual keyboard to the bottom of the viewport using position: fixed instead of inline flow inside the modal
  • Add padding-bottom: 280px to the keyboard-active modal to prevent content from being hidden behind the fixed keyboard
  • Increase compact search results max-height from 120px to 50vh so 5-6+ results are visible above the keyboard

Context

On the kiosk touchscreen, only ~2 search results were visible because the inline keyboard consumed most of the modal's vertical space. By fixing the keyboard to the viewport bottom and letting the search results expand, guests can now see many more results without scrolling.

Test plan

  • Desktop browser: open /e/{code}/display → "Request a Song" → no virtual keyboard, search results display normally
  • Touch simulation (DevTools): keyboard pins to bottom of viewport, search results fill space above it
  • Pi kiosk: 5-6+ search results visible above the keyboard
  • Keyboard taps still work (still a DOM child of modal, events propagate correctly)
  • Modal close (X, overlay click) still works with fixed keyboard

Move keyboard from inline flow to position:fixed at the bottom of the
viewport. Add padding-bottom on the modal to prevent content hiding
behind the keyboard. Increase compact search results max-height from
120px to 50vh so 5-6+ results are visible above the keyboard.
@thewrz thewrz merged commit af05ff1 into main Feb 24, 2026
8 checks passed
@thewrz thewrz deleted the fix/keyboard-fixed-bottom branch February 24, 2026 00:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant