Keyboard not displayed on iPad when focus is set (tap) on ComboBoxItem

[fkamthong]

1) SmartClient Version: v10.1p_2016-06-14/Pro Deployment (built 2016-06-14)
2) Safari on iPad, iOS 9.3.2
6a) gwt.xml:

<?xml version="1.0" encoding="UTF-8"?>
<module rename-to='app'>
<inherits name="com.smartgwtee.SmartGwtEE"/>
<entry-point class='test.client.TestComboBoxItem'/>
<source path='client'/>
</module>


6b) test/client/TestComboBoxItem.java:

package test.client;

import com.google.gwt.core.client.EntryPoint;
import com.smartgwt.client.widgets.form.DynamicForm;
import com.smartgwt.client.widgets.form.fields.ComboBoxItem;
import com.smartgwt.client.widgets.form.fields.SelectItem;

//
// Tested against:
// SmartClient Version: v10.1p_2016-01-12/Pro Deployment (built 2016-01-12)
// SmartClient Version: v10.1p_2016-06-14/Pro Deployment (built 2016-06-14)
//
public class TestComboBoxItem implements EntryPoint {

public void onModuleLoad() {

SelectItem selectItem = new SelectItem("selectItem", "SelectItem");
selectItem.setBrowserInputType("text");

ComboBoxItem comboBoxItem = new ComboBoxItem("comboBoxItem", "ComboBoxItem");
comboBoxItem.setBrowserInputType("text");

DynamicForm dynamicForm = new DynamicForm();
dynamicForm.setItems(selectItem, comboBoxItem);
dynamicForm.draw();
}

}

[Isomorphic]

We're not seeing an issue. Please describe exactly what's going wrong for you.

Also, please try removing your attempt to set browserInputType - at best, that would do nothing, at worst it might break something (whatever it is that's going wrong for you).

Finally, let us know if you see an issue with ComboBoxItems in the online showcase.

[fkamthong]

The latest showcase handles this properly (in most cases) with its adaptive UI.
http://www.smartclient.com/smartgwte...ing_validation

But, the problem is with the older 5.1 versions - Version 6.0 has a similar issue though.
See http://www.smartclient.com/smartgwt/...bobox_category
- Tap on the "Items" field to enter new values

In the showcase above, the cursor is where the TextItem would be but is covered by the picker and the keyboard does not come up.


In version 5.1, the cursor is in the TextItem but the software keyboard does not come up.

Setting the browserInputType property has no effect (negative or positive - tried with and without the property)


Regards,

Frederic

[Isomorphic]

Just a quick note to reassure you that we are working on this - we are reproducing the problem and expect to have a fix in the next day or two

Regards
Isomorphic Software

[Isomorphic]

This problem is now fixed in SmartGWT versions 5.0 and greater (SmartClient 10.0 and greater). Please retry your use case with tomorrow's build of one of those versions, and let us know if you still see any issues

[fkamthong]

I just tried the Showcase application: http://www.smartclient.com/smartgwt/...bobox_category
The version information displayed by the Showcase application is:

Version: 6.0p
Built Thu Jul 07 05:31:00 GMT-400 2016


I am able to select the 'Allow New Values' option and enter new values from a desktop web browser.
From an iPad, the picker is displayed when I tap on the text editor portion of the 'Items' ComboBoxItem. I cannot enter a new value.

The keyboard is still not being displayed when running the sample code I have provided in the first post.

For the Showcase application, the version string displayed by the SmartClient Developer Console is: SmartClient Version: v11.0p_2016-07-07/LGPL Development Only (built 2016-07-07)
For my test application, the version string displayed by the SmartClient Developer Console is: SmartClient Version: v10.1p_2016-07-07/Pro Deployment (built 2016-07-07)

[Isomorphic]

The problem we were referring to was specifically the issue of the cursor appearing in the comboBox, and burning through the picklist. When running on a mobile device, comboBox items are made readonly, so you should not be able to enter text in them, and neither the cursor nor the software keyboard should appear. This is deliberate - on a mobile device the picklist is full-screen, so the comboBox item itself will always be occluded by the picklist. Instead, you can enter a new value in the "Search" field of the picklist and then tap the "Accept" button (this only appears if your comboBox has set "addUnknownValues" true). Note, the Showcase sample you refer to does not work quite as intended on a mobile device, because the "Allow New Values" toggle is not being correctly dynamically applied. Your own code will not have this problem if it calls setAddUnknownValues(true) during initialization, rather than toggling it at runtime like our sample does. Either way, this has also now been fixed.

Reviewing this, we feel it is perhaps not clear enough that the "Search" field on a full-screen popout picklist is also intended for entering new values, so we are introducing a new property so the in-field hint can be different if new values are allowed, than if it is purely just a search field. This will only be introduced as far back as 6.0, but be aware that the hint in that field is already configurable if you want to change it - the change we are adding is to make it separately configurable for the two different cases, new values allowed / not allowed. For the existing functionality, see setPickerSearchFieldHint()

[fkamthong]

That kinda makes sense. Thank you for the explanation.

However, just as a FYI, the blinking cursor is still poking through the fullscreen picklist in the following example:
http://www.smartclient.com/smartgwt/...bobox_category

The cursor for the 'Custom' ComboBox can still be seen through the grid.
On the first ComboBox, the cursor is appearing in the search field - you have to tap on the hint before you can type...

[Isomorphic]

We've made an additional change to "fix the fix", which should be available in tomorrow's nightly build (July 12), in 6.0 and 6.1d

Regards
Isomorphic Software