Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

keyboard does not show up on an iPad/iPhone in Mobile Safari #21

Open
shazron opened this issue May 12, 2014 · 3 comments
Open

keyboard does not show up on an iPad/iPhone in Mobile Safari #21

shazron opened this issue May 12, 2014 · 3 comments

Comments

@shazron
Copy link

shazron commented May 12, 2014

The keyboard does not show up on an iPad/iPhone when using Mobile Safari, preventing the user from entering search data in the search field, which is the point of the whole website.

Expected:
When touching the search field to bring it into focus, the keyboard should be visible so the user can enter search terms.

Actual:
When touching the search field to bring it into focus, the keyboard is not visible, and the user cannot enter search terms.

Environment:
iPad 3 with iOS 7.1
iPhone 5s with iOS 7.1.1

@shazron
Copy link
Author

shazron commented May 12, 2014

One clue, the input tag seems to be 4px in length:
screen shot 2014-05-12 at 10 01 05 am

@shazron
Copy link
Author

shazron commented May 12, 2014

Some more data:
On a desktop browser, it looks like the website is auto focusing to the search field on load. This will not work on Mobile Safari since the keyboard display requires user interaction, not programmatically (unless you are using your own UIWebView, where you can enable a property so you can do this). So there might be assumptions somewhere that did not take into account Mobile Safari's behaviour.

@3rd-Eden
Copy link
Member

The main problem is that the library that we use for the autocompletion does not seems to function on mobile as intended. The field is only focused once the search-pagelet is rendered in the DOM.

There are different ways around this problem:

  1. Disabling the autocomplete completely for mobile & show an input element instead.
  2. Use a different library for the autocomplete that does work correctly with mobile. The only requirement it has is that we can implement a custom autocomplete/request function so all data will be send over RPC (WebSockets)

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

No branches or pull requests

2 participants