Fix mobile search bar keyboard issue on Android browsers #1452
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
The search bar on mobile browsers (Chrome/Firefox on Android) was not showing the soft keyboard when tapped, preventing users from entering search terms. This only affected mobile browsers - the desktop site worked correctly.
Root Cause
The NcSelect component's input element was missing mobile-specific attributes and proper touch event handling needed to trigger the virtual keyboard on mobile devices.
Solution
Added minimal changes to
SearchField.vueto enhance mobile compatibility:1. Mobile-specific input attributes
2. Enhanced touch event handling
3. Improved focus() method with mobile detection
Testing
The fix has been verified to:
This addresses a regression since mobile keyboards previously worked, building on the mobile browser fixes from version 0.1.2 and mobile improvements in version 1.1.0.
Fixes #1337.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.