Scrollview pager/render issues

4 posts, 0 answers
  1. Marlon
    Marlon avatar
    16 posts
    Member since:
    Jul 2013

    Posted 24 Oct 2013 Link to this post

    http://jsbin.com/otImETiQ/20/

     I want for have two separate ScrollViews on a page but there seem to be some glitches:

    1. When the page first loads, an extra portion of the component is visible. I had to work around this with window.trigger('resize'); If there's a smarter way please let me know.
    2. If I apply padding to the scrollview, the div does not position itself correctly initially. It snaps into position after you attempt to interact with the widget.  (I found a workaround to by setting a translate param to the first child div) 
    3. The bottom scrollview isn't visible initial until the user starts to interact.
    4. For the bottom scrollview. With 3 data items, I'd expect to be able to page swipe to the 2nd page. That doesn't seem to work. The 3rd item doesn't appear to have been created.
    5. The pager for both show the number of items in the data source rather than the number of page.
    Please any suggestions are welcome.

    Thank you

  2. Petyo
    Admin
    Petyo avatar
    2439 posts

    Posted 25 Oct 2013 Link to this post

    Hello Marlon,

    Thank you for contacting us. The issues you exhibit are actually a combination of unsupported scenarios (paging with local data) and some bugs on our side (the second page should actually be visible, for example). The good news is that we are going to address the unsupported with our Q3 release. Thanks to your report, we are going to look into addressing the bugs in this case, too. 

    Unfortunately, I can't suggest a viable workaround for this particular case, though. The Q3 release is expected in the second part of November.

    I am updating your telerik points for this finding. 
     
    Regards,
    Petyo
    Telerik
    Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
  3. Kendo UI is VS 2017 Ready
  4. Marlon
    Marlon avatar
    16 posts
    Member since:
    Jul 2013

    Posted 25 Oct 2013 Link to this post

    My data is coming from a remote call. I just hard coded it for the example. Assuming I have this wired to a remote dataSource, can you please let me know which issues I can resolve?

    Thank you.
  5. Alexander Valchev
    Admin
    Alexander Valchev avatar
    2875 posts

    Posted 29 Oct 2013 Link to this post

    Hi Marlon,

    Binding the widget to remote dataSource will not resolve the issues you encountered. As my colleague Petyo explained they are caused by a combination of currently not supported scenarios, e.g. the reason for the issues is not only the type of data that you work with.

    At present I can suggest a workaround only for the 3rd problem:
    3. The bottom scrollview isn't visible initial until the user starts to interact.

    To fix that, you should make the scrollview widget element relatively positioned with CSS. Just add the following to the style sheet of your project (we will include this fix in the next release).
    .km-scrollview {
        position: relative;
    }

    Regarding 4th issue:
    4. For the bottom scrollview. With 3 data items, I'd expect to be able to page swipe to the 2nd page. That doesn't seem to work. The 3rd item doesn't appear to have been created.

    Currently the widget renders only pages that have full set of items per page. In your case, in the DataSource there is only one record left while the widget has to render 3 items. We consider this as a bug and will fix it for the next official release. Unfortunately I cannot suggest an easy workaround since the fix requires changes in the source code of the framework.

    The same applies for issue #5. We will investigate further the behavior in cases #1 and #2.
    Once again, please accept my apology for the inconvenience caused.

    Regards,
    Alexander Valchev
    Telerik
    Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
Back to Top
Kendo UI is VS 2017 Ready