The reported problem has been submitted to Crosslight development team and filed under work item CROS-373. I will keep this thread updated with any news I heard from the team regarding CROS-373.

Is this bug already fixed?

What is the current state of the bug, what priority has this bug, how can I check this?

We have recently released hotfix for Crosslight 2 Update 2 on June 30, 2014. The hotfix includes the fix for CROS-373.

To read the detail of what included in this hotfix, please check Crosslight 2.0 Update 2 Release Notes at http://developer.intersoftpt.com/display/crosslight/Crosslight+2.0+Update+2+Release+Notes.

Kindly check Updating Crosslight page at http://developer.intersoftpt.com/display/crosslight/Updating+Crosslight to get the detail information about how to obtain and apply updates to your project.

Please let us hear your feedback whether it helps or not.

CROS-373 is not mentioned in the fix list. How should I have a chance to see if this bug is fixed?

Please find the attached video which shows how the problem, content of the view does not scroll down, is no longer persist on MVVM Sample. It seems there is a problem with the system to generate the fix list which causing CROS-373 doesn’t include in there.

Please let me know if you have different result.

Hello Yudi,

I think it works. On iOS it is fine. On Android the scrolling is fine, too. When I go to "Binding Mode" and enter some text in the text field and click in the number field the text under "one-way binding" is the same as entered in the text field. But when I enter text in the text field and press the hardware back button the text under "one-way binding" is not updated. Maybe this is the desired behaviour on Android, but the binding is definitely out of sync.

The MVVM Sample – Binding Mode is work as expected on Android. The text field – under “one-way binding – will get updated on lost focus. In iOS, press Return will close the keyboard and remove the focus from the text field.
However, Android has different behavior. Closing the keyboard doesn’t remove the focus from the text field.

Hope this help.

Thanks Yudi,

I think we can close this bug.

Glad to hear the good news regarding the reported problem.

Should you need further assistance or run into any problems regarding our products, feel free to post it into our forum. We would be happy to assist you again.