Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scrolling large OnDemand grids #110

Closed
scbird opened this issue Mar 3, 2012 · 4 comments
Closed

Scrolling large OnDemand grids #110

scbird opened this issue Mar 3, 2012 · 4 comments

Comments

@scbird
Copy link
Contributor

scbird commented Mar 3, 2012

There appears to be an issue with OnDemand grids that have many rows. It is impossible (or at least extremely difficult) to scroll to the bottom of them - when dragging it, the scroll bar doesn't correctly follow the mouse. It appears that the height of the grid (or at least the scrolled area) does not correctly reflect the total number of rows returned by the store, and that it is being expanded as you scroll down.

This can be seen in dgrid/test/performance.html - you cannot scroll properly to the last row. This problem doesn't occur in the equivalent page for dojox.Grid.

@ghost
Copy link

ghost commented Mar 6, 2012

This is unfortunately due to how the OnDemandList module is presently designed. It's something I'll be sure to bring up in discussion again, but for the time being, you should be able to mitigate this behavior to a degree by playing with the maxEmptySpace property in the arguments passed to the constructor. (It defaults to 10,000 px.)

scbird added a commit to scbird/dgrid that referenced this issue Mar 11, 2012
ColumnSet.renderArray() now handles Deferreds
Added row buffer to OnDemandGrid to increase perceived performance
Fixed row reordering bug in Chrome (_StoreMixin.js)
@ghost
Copy link

ghost commented May 14, 2012

Whoops, didn't realize this was still hanging open; this has been resolved by #132 (which includes #117).

@ghost ghost closed this as completed May 14, 2012
@scbird
Copy link
Contributor Author

scbird commented May 14, 2012

Actually it may still be open - I think there are still issues in #132 (which are resolved by the two last commits in #117, which I'm pretty sure weren't included in #132), but I haven't had time to check it yet. If the issues still exist I'll reopen this ticket.

@ghost
Copy link

ghost commented May 14, 2012

OK, thanks. I was initially under the impression those had been resolved based on Kris' response, but by all means, let us know if you still see issues. Thanks for your contributions!

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant