Finding it difficult to select a value from the DDL in landscape mode(in iOS8) as the page moves up and down due to the keyboard that auto appears. This happens for the sample provided for igcombo in igniteui website (url given below)
http://www.igniteui.com/combo/overview
Please let us know how to resolve this at the earliest.
Thanks
Ramya Y
Hello Ramya Y,
Thank you for posting on our forums.
The behavior you encounter with the igCombo is expected because the mode option is set to editable by default. If you don't want the keyboard to appear, please set the mode option to dropdown.
To learn more about the mode option, please review the API documentation linked below:http://help.infragistics.com/jQuery/2014.2/ui.igcombo#options:mode
Please let me know if you have any questions regarding this matter.
Hi Jose,
Thanks for responding. I really appreciate all your support today
We tried the option you mentioned, but unfortunately we lose the filter option under that case. We would like the filter option. Please investigate why under IOS8 the drop down appears and disappears sometime, appears sometime and most importantly only selected the proper drop down list value when the keyboard is raised.
All the above issues are not happening on IOS7, but appearing in IOS8.
please conduct your analysis to confirm this is not a feature or expected behavior. We have a prod rollout soon and would like to have this working. In the mean time, we will continue to discuss the workaround you presented, albeit its limitations for our use case.
Rich
Hi,
I have investigated this issue further and noticed there is a difference in behavior between Chrome and Safari for iOS 8. I have asked the team for this control to examine this further. To ensure that it will receive attention, I have logged this behavior in our internal tracking system with a Development ID of 189817. The next step will be for a developer to review my investigation and confirm my findings or to offer a fix, or other resolution. Note, I was not able to reproduce this in an iOS7 device because I don't have one available; though I have noted on the Development ID that it is believed to work as expected in iOS7.
I will be sure to update this thread once a solution is available for this issue.
We have completed our investigation and have determined this to be an issue with iOS. We've created a bug with Apple that was mark as duplicate and then closed. Its my understanding that apple will fix this issue and provide the fix in a future release of iOS.
If you have additional questions regarding why this issue occurs with Safari, you may contact Apple Support.