android back button and kendo back button

[Dean]

I've noticed that while at first the android back button (as on an android device) and the kendo mobile back button appear to work the same way, when you use a combination of both you get different behaviour. Let's see how I go at explaining what I mean...

I have 3 views; view-a, view-b and view-c. I start the application and the initial view is view-a, then I do the following tests:

Android back button only

1. navigate to view-b
2. navigate to view-c
3. use the android back button - takes me to view-b
4. navigate to view-c
5. use the android back button - takes me to view-b
6. use the android back button - takes me to view-a

Kendo back button only

1. navigate to view-b
2. navigate to view-c
3. use the kendo back button - takes me to view-b
4. navigate to view-c
5. use the kendo back button - takes me to view-b
6. use the kendo back button - takes me to view-a

Both the kendo and android back buttons

1. navigate to view-b
2. navigate to view-c
3. use the kendo back button - takes me to view-b
4. navigate to view-c
5. use the kendo back button - takes me to view-b
6. use the android back button - takes me to view-c
7. use the android back button - takes me to view-b
8. use the android back button - takes me to view-c
9. use the android back button - takes me to view-b
   
10. use the android back button - takes me to view-a

Notice the extra steps when using first the kendo back button and then the android back button? FYI, the same happens when using android first and then kendo. Ideally what would happen is the same behaviour as in the first 2 scenarios.

Why would I want both back buttons available you ask? Well I've implemented a swipe gesture that fires navigate("#:back") for convenience because reaching for the back button on a tablet can be a stretch.

So, any ideas? Is this something that would need to be fixed/developed in kendo mobile or is there something I can do?

[Petyo]

Hello Dean,

Thank you very much for the thorough test case. I managed to reproduce it in a regular desktop browser, too (the sample I used is here). This is definitely a problem that should be addressed in Kendo UI Mobile, and it stems from  the way the application pane history stack "communicates" with the browser history object. We will try to address the problem in our upcoming internal builds. Unfortunately, I can't provide a viable workaround for the problem right now.

I am updating your telerik points for this finding. Thank you once again. 

Regards,
Petyo
Telerik

[Rodrigo]

Is ther a solution to this problem?

[Petyo]

Hi Rodrigo,

This thread is several months old and discusses an issue with our Q2 release. The problem should be resolved in Q3 2013 and newer subsequent releases. 

Regards,
Petyo
Telerik