Re: Live Scroll - Usability Testing Feedback and Design Guidelines

Cindy Lu <[email protected]>
Newsgroups gmane.comp.web.chi-web
Message-ID <[email protected]>
Aras,

Thank you so much for sharing the online demo and your thoughts on the list
of related issues.  Our application has come up with a similar grid with
our visual style but without the message "Please Wait" and the masking
effect.

I noticed that demo displayed the range of visible records as you scrolled
the table and the scroll bar did not jump back.

I received several complaints from users about the scroll bar jumping
back. Showing the user what record(s) she is looking at is important too.
So, we added the row count column.  I think showing the range of records is
nice to have.  However, I will need to gather some user data on this feature
too.

I will share the demo, forum and blot sites with our developers.

Thanks!

- Cindy

On 3/3/08, Aras Kannu <[email protected]> wrote:
>
> The product we use inside of our framework will probably come out with a
> LIVE GRID implementation. Here is a demo that someone has put together
> http://www.siteartwork.de/livegrid_demo/
> His Blog may give your dev team some ideas on his implementation
> (although the technology may be different from yours)
> http://www.siteartwork.de/2007/11/10/livegrid-component-with-extjs/
>
> I have not come across any formal design guidelines for live grid.
>
> However, I do think that the scrollbar jumping back is a major issue. As
> far as informing the user about what the range is they are viewing, I am
> wondering if it is necessary in all cases. If you display a "Total
> records: #####" at the bottom on initial display of the grid, do you
> need to constantly tell the user what specific range they are looking
> at? I remember reading that it is expensive to calculate with every
> scrollbar movement. In many cases, those numbers (range) may not mean
> much to user other than just providing a mere comfort feeling.
>
> -aras
>
> -----Original Message-----
> From: ACM SIGCHI WWW Human Factors (Open Discussion)
> [mailto:[email protected]] On Behalf Of Cindy Lu
> Sent: Wednesday, February 27, 2008 10:30 PM
> To: [email protected]
> Subject: Live Scroll - Usability Testing Feedback and Design Guidelines
>
> Hi!
>
> We have incorporated live scrolling function (or infinite scroll) into a
> beta product.  We observed some issues from users such as the scroll bar
> jumps back when scrolling down, how to inform the user the range of
> visible
> records, etc.
>
> Have you used the live scroll feature in your product?  Do you have any
> lessons learned that you can share?
> Do you know if there are any design guidelines for this function?
>
> Thanks!
>
> - Cindy
>
>    --------------------------------------------------------------
>           Tip of the Day: Postings must be in plain text
>     CHI-WEB: www.sigchi.org/web POSTINGS: mailto:[email protected]
>              MODERATORS: mailto:[email protected]
>       SUBSCRIPTION CHANGES & FAQ:  www.sigchi.org/web/faq.html
>    --------------------------------------------------------------
>
>    --------------------------------------------------------------
>        Tip of the Day: Forward out-of-office replies to
>                    mailto:[email protected]
>     CHI-WEB: www.sigchi.org/web POSTINGS: mailto:[email protected]
>              MODERATORS: mailto:[email protected]
>       SUBSCRIPTION CHANGES & FAQ:  www.sigchi.org/web/faq.html
>    --------------------------------------------------------------
>
>

    --------------------------------------------------------------
        Tip of the Day: Forward out-of-office replies to
                    mailto:[email protected]
     CHI-WEB: www.sigchi.org/web POSTINGS: mailto:[email protected]
              MODERATORS: mailto:[email protected]
       SUBSCRIPTION CHANGES & FAQ:  www.sigchi.org/web/faq.html
    --------------------------------------------------------------
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.