Latest Version of Graphite not fit for purpose.

[Paul]

Today my Graphite has updated and now my app is riddled with issues.

Using the flat theme the nav bar interferes with the status bar and looking at your updated kendo ui version sample project it looks like I now have to add statusBarStyle = os.ios && os.flatVersion >= 700 ? "black-translucent" : "black"; for it to display correctly. Secondly I notice the version of kendo UI v2013.2.1021 was in fact a internal release which even states should not be used for production and had already been replaced by a new internal version. Kendo team don't even seem to have released this version themselves. So I have to say I'm a little confused as to why you are shipping that version with icenium. Now I could probably live with the above as once you work out you need add the status bar code it sorts that issue.

However and you can use the latest Kendo sample project that the new graphite has to replicate this major issue and that is when you click in any text box the new style keyboard comes up and destroys the screen as in the taskbar moves up to above the keyboard and the textbox disappears out of view and looses focus. On the Kendo sample app click the logon and then try and type something into the username box. I have had a debug version built in the last version of Icenium that has just been approved to compile a production one for the app store but how can I now when this version of Icenium has just shafted my project.

As you can probably tell I'm little annoyed as I will have to tell my bosses that I can not move to production and that they may have to run through testing again.

Please Icenium Team how can I resolve this?

Thanks 

 

[Paul]

From what I have read it seems the keyboard issue is related to Cordova 3.0 and IOS7 SDK. Cordova 3.1 has some fixes for this issue and Cordova 3.2 has gone one step further by removing the Keyboard stuff out and put into a plugin.

However the issue still remains for me and will for others until either the cordova version in Icenium is moved up or perhaps a new option in Icenium that would allow the choice of which SDK version to compile against.

Do you have any recommendations as to what I can do short term to resolve this as not being able to move an app to production because of this is embarrassing.

Have you been able to replicate it and confirm what I'm saying, just so I know I'm not doing something wrong.

Thanks 

[Jean-Paul]

I am having the exact same issue, my app is using a barcode scanner plugin so my cordova version is 2.4. I'm using the flat skin and my status bar is having the same issue. My application contains tabstrip so anytime a textbox is invoked for entry the tabstrip slides up above the keypad and it seems the keyboard event handler does nothing. The simulator does not show this issue, when it is deployed to a device are when these problems occur. The latest version created two weeks prior worked perfectly, I even resorted back to that version and still the same issues occurs with the latest graphite build. Any guidance on[quote]Your quote goes here[/quote] how this could be resolved would be greatly appreciated. I have attached a screen shot from the IOS device.

Thanks

[Svetlio]

Hello Paul,

 
Unfortunately the problem comes from iOS7 and is not related to the latest Kendo UI or Icenium Graphite.

We could offer you two workaround solutions.

The first option is to activate Kendo UI native scrolling option:

new kendo.mobile.Application(document.body, {
layout: "tabstrip-layout",
statusBarStyle: statusBarStyle,
useNativeScrolling: true
});

and change the footer position in the views with inputs to absolute:

#tabstrip-login .km-footer {
    position: absolute;
}

The second option is to attach event handlers to the input fields and hide the footer on focus:

document.addEventListener('deviceready', function () {
      navigator.splashscreen.hide();

      $("input").on("focus", function () {
         $(".km-footer").hide()
      });

      $("input").on("blur", function () {
         $(".km-footer").show()
      });
}, false);

Regards,
Svetlio
Telerik
You've missed the Icenium Visual Studio Integration keynote? It has been recorded and posted here.
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.

[Paul]

Hi Svetlio,
                     Your first suggested option does resolve the issue but have native scrolling on application wide breaks the app in other places.

Option two does not work even on the kendo sample application as it seems when inputs are in a ul with data-role="listview" data-style="inset" the focus event never gets fired. Take them out of the data attributes and it does fire but the input does not get brought into view.

I think when you released this version of icenium you should of included a newer version of cordova and had that one use the IOS7 SDK and people that were already using Cordova 3.0 in icenium should have stayed using IOS6 SDK and left it up to them to move up rather than being forced to use the IOS7 SDK. Is there no way to have a option of which IOS SDK we want to compile against.

Do you have any other suggestions that may help?

Thanks
 

[Stewart]

I agree this is most vexing, but for me the first solution presented by Svetlio resolved the problem, so I am happy enough for now.

Paul, so I understand, what are the potential issues with native scrolling that I should look out for?

Stewart

[Stewart]

In fact, this does not seem to have resolved the issue. This is what I have done, which has partially solved the problem, but not fully, which is where I need help, please.

Here is the textarea markup which hides the footer on focus and shows it again on blur:

<textarea data-bind="value: comment"
id="newComment" rows="6"
style="background-color: #FFFFFF; border-style: solid; border-width: 1px; width: 98%"
onFocus="$('.km-footer').hide();"
onBlur="$('.km-footer').show();">
</textarea>

This works fine on the simulator and also when connecting my iPad directly to my laptop during devel.

HOWEVER, when I make a build and distribute it through testflight, this functionality does not work correctly. Any ideas, or even better, a proper solution to this most vexing problem?

*EDIT*
What seems to happen is that I click on the textarea, which brings up the keyboard, but the textarea then loses focus, so the footer/navigation appears again. If I then subsequently click on the textarea again, the footer disappears as expected... Very odd. Any thoughts?

Stewart

[Steve]

Hi Stewart,

The colleagues from Kendo UI team are aware of this problem and working on a fix. For the time being you would have to apply nasty hack like the one pointed by Audrey in this forum post.

Regards,
Steve
Telerik
You've missed the Icenium Visual Studio Integration keynote? It has been recorded and posted here.
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.

[Stewart]

Thanks Steve.

Is there an estimated date for a fix as this is very inconvenient. For me, neither of the hacks in this forum post fixed the footer sliding up; I have got around it by hiding the footer on pages where there is a text entry, but it's hardly ideal. I have also seen another problem whereby a textarea hidden by the keyboard sliding up loses focus, which I can't solve, but will post about on the other forum (unless you can answer it here?)

Stewart

[Steve]

Hello Stewart,

I've attached a sample project that utilizes similar fix to the suggested one in the other forum. Please review it and let me know if further help is needed.

Regards,
Steve
Telerik
You've missed the Icenium Visual Studio Integration keynote? It has been recorded and posted here.
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.