I'm just curious if anybody else has been having issues with the Web Data Grid on devices running iOS 8 and if anybody knows what Infragistics official position is on iOS 8? Are they saying iOS 8 is unsupported at this point with a service release in the works that will support it down the line or do they say that iOS 8 should be supported in 13.2 and 14.1 at the present service pack level? If a service pack is in the works any idea on a time frame? Are we talking days, weeks, months, etc?
I've been testing my site in Safari on the latest publicly released build of iOS 8 and I'm noticing some major data entry issues. I've got two Web Data Grids located on two different tabs within a Web Tab control. I have the following behaviors enabled in both grids: Activation, Editing Core (with Cell Editing under the Editing Core enabled but nothing else), Row Selectors and Selection. Under the Editing Core - Cell Editing Behavior I've got the following settings for EditModeActions: EnableF2 - False, EnableOnActive - True, EnableOnKeyPress - True, MouseClick - Single. Both Web Data Grids have AJAX enabled.
These settings worked wonderfully under iOS 7. The user would touch the cell they wanted to edit, it would become active in edit mode and they could use the grid in the same manner they can in IE, Firefox and Chrome with all of the Grid Editor Providers in use working as expected. iOS 8 is a different story. I've noticed the following behavior:
1) In a cell with a Drop Down Grid Editor Provider the user can touch the cell, it will become active and the Drop Down provider will display but when you then try and touch the drop down provider to show the list of values suddenly the active cell changes from the cell you touched to either the cell in the row below, or in some cases two rows below. You then have to touch back into the original cell you wanted in the first place and repeat the process.
2) Possibly related to 1, the cell with the Drop Down Grid Editor Provider happens to be the first cell on the Web Data Grid so users naturally tend to touch that cell first to start entering data. When you initially tap into the cell and it becomes active Safari will automatically zoom in on the grid. I'm assuming that is to try and bring the cell into focus and make entering data into it easier for the end user. The problem is when it does that it zooms on the wrong portion of the page. It zooms in on the column heading instead of into the first cell on the grid. The cell in question isn't visible at that point and you have to zoom back out a bit manually and then touch the cell you want again. It only seems to do this the first time the grid / cell becomes active. After that I don't notice that behavior again even when clicking back into the same cell on the grid.
3) In a cell with a Numeric Grid Editor provider when I touch into the cell the cursor appears to the right of the value in the cell (which defaults to zero) even though I have the SelectionOnFocus property set to SelectAll. It will only actually select the value in the cell so it can be overwritten if you then touch into the cell again a second time.
Yes, I have asked the developers to make sure that this gets logged with Apple.
That's kind of what I figured. Some of the strange behavior I first encountered using the controls under Safari in iOS 8 when it was first released have since been fixed with subsequent updates from Apple but there are still issues. Will your developers be submitting a bug report to Apple about it?
Troy,
After further research in to the behavior it looks like this is a bug in Safari itself on iOS8 and not within the WebDataGrid. Infragistics does officially support Safari on iOS8 but this is an issue that will need to be fixed in the Safari browser rather than the Infragistics controls. Please let me know if you have any questions about this behavior.
Hi Troy,
I have created a private support case for you for these issues and will follow-up with you on the private support case,
Thanks!
Just an update in the interim I've tested the site with Chrome under iOS 8 and none of these issues appear so as far as I can tell they are related to changes in Safari between the iOS 7 and iOS 8 versions although the new iOS 8 keyboard may play a role as well since the Chrome App on iOS 8 uses it's own in-app keyboard that is different from the iOS keyboard. Let me know if you need me to provide a sample that demonstrates all of the issues I've outlined above. I've got one I can provide if you need it. Thanks for your help on this!