24 Answers, 1 is accepted
We are not aware of such issue in ListView for Kendo UI Mobile. Could you please provide a URL or a sample project where this occurs? Thus way we will be able to reproduce the problem and assist you further.
Thank you in advance!
All the best,
Iliana Nikolova
the Telerik team

Cheers,
Simeon
This seems like one of the known limitations of the pull to refresh feature - the content area has to be larger than the contents, so that scrolling can be performed.
As a workaround, I may suggest that you extend the listview height to something larger, so that scrolling will always be enabled.
Greetings,
Petyo
the Telerik team

It can happen there is just not enough (dynamic) data to display, but still a refresh would be necessary. Just putting extra placeholders is a dirty workaround :)
Indeed, a padding item is a workaround. However, having a pull-to-refresh for content less than the page would enable scroller for an area that is otherwise non-scrollable. This may cause confusion for the end user.
Kind regards,
Petyo
the Telerik team

Do you expect that this will be fixed soon? I have a similar problem. I dynamically build a listview and cannot predict how much data will actually be returned. I depend on the pull to refresh capability to let a user refresh the list. But if the list isn't longer than the viewport, then the user cannot use pull to refresh so there is absolutely no way to get out of this situation by the user. I can do the margin-bottom workaround on the list view but it does as you say -- makes the window scrollable for a bunch of white space at the bottom that makes for a poor user experience.
Regards,
Patrick
The feature is in our backlog for our Q2 release.
Greetings,Petyo
the Telerik team

Thank you for your response! Could you clarify if "backlog for Q2 release" means that you plan to fix it for certain or if it just a candidate that may or may not be fixed depending on other priorities? I've been trying to come up with a workaround that adds just enough margin to fill up slightly more than the page but I have not had success. The workaround needs to account for all shapes and sizes of target device screens (all iOS and Android), orientations (portrait/landscape) and variable data in list views. It would be much better if your talented team could supply a fix. As you can see, I purchased the library and so far I am very happy. Hoping this will be fixed.
Regards,
Patrick
Sorry for not being clear enough.
Being in the backlog in this case means that we are looking into addressing it for the next release, but we can't really commit to that (committed features are found in our roadmap).
To be completely honest, the biggest reason for that is, that we are still not sure how to fix that in a reliable manner.
Personally, I hope that we will come with something, as this seems like somewhat common case.
Petyo
the Telerik team

http://jsfiddle.net/RodEsp/ZqMNG/15/
Do you have any proposed workarounds?
Data attributes are translated to dashes, so the attribute be data-pull-to-refresh. However, while testing, I noticed that indeed a declarative attribute setting of the pull-to-refresh does not work. This problem will be addressed in our next internal build, coming out end of this week.
The mobile listview widget does not have a selectable option (please refer to the docs) - perhaps you have discovered an error in our documentation or demos? Can you please point us to the place where you have seen that option?
Petyo
the Telerik team

I am excited about the recent release of Kendoui's new version. However, I am still experiencing some difficulties trying to implement the pull-to-refresh attribute in a listview.
Here's a jsfiddle where it seems like the attribute is ignored.
http://jsfiddle.net/RodEsp/p9UQW/
When I add that attribute to my real application and try to run it in a browser or a mobile device the app freezes on the view before the following console error: Uncaught TypeError: Cannot call method 'pullHandled' of undefined. Can you provide any clarification on this?
Thank for all your help.
The fiddle that you provide does not uses a version from 15th May (Q1 SP1). I tested the data-pull-to-refresh attribute with the latest release (Q2 2012 Beta) and did not managed to reproduce the problem.
<
ul
id
=
"listview"
data-role
=
"listview"
data-source
=
"dataSource"
data-pull-to-refresh
=
"true"
data-append-on-refresh
=
"true"
data-template
=
"pull-to-refresh-template"
>
</
ul
>
Could you please check my test page and point out what I am missing?
Regards,
Alexander Valchev
the Telerik team

However, after upgrading to the Q2 version I have the same issue that I do on my real app. When trying to navigate or load the view that contains the listview with the data-pull-to-refresh attribute, the page/app freezes.
The console now reads: Uncaught RangeError: Maximum call stack size exceeded.
I have updated the jsFiddle and commented out the data-pull-to-refresh attribute since the page won't load with it enabled.
http://jsfiddle.net/RodEsp/p9UQW/
You can easily reproduce the issue by simply adding the attribute to the listview.
I believe the problem is caused by the dataSource configuration - your example uses jsFiddle echo service to simulate Json call and is not page-able. Does the problem persists if you use a remote data service and dataSource with serverPaging enabled?
Please provide such reproduction project and I will check it right away. Thank you in advance for the cooperation.
Regards,
Alexander Valchev
the Telerik team

How exactly must serverPaging be implemented on the server-side?
Simply declaring serverPaging: true on the dataSource doesnt seem to solve the issue ^^'

Have someone found a solution?
is a vary big limitation.
Thanks Dario
I am glad to inform you that the issue where the contents are shorter than the viewport disables the pull to refresh is resolved, and will be available in our next internal build, due next week. I would like to thank you guys for the patience and cooperation.
Greetings,Petyo
the Telerik team


we'll wait next week to start testing.
Thanks a lot!!
Dario.

I have been half day fighting with this issue...

And does anyone know if the problem with pull-to-refresh in connection with endless-scroll was fixed yet?

I downloaded Q3 beta, and it´s already working.
Waiting for definitive version.
