-
Notifications
You must be signed in to change notification settings - Fork 354
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
Fix vertical scroll indicator placement #859
Fix vertical scroll indicator placement #859
Conversation
d071cb4
to
5d0904a
Compare
return generateRows(1); | ||
return generateRows(100, 1, (row, key) => { | ||
return String.fromCharCode(key.charCodeAt(0) + 7); | ||
}); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By making this change here, have we lost test coverage for cases where the footer rows are not scrollable?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change only affects the example in the docs. We could include an example for each case (single footer row vs. many scrollable), but this effectively demonstrates everything the bottom indicator does.
It's fair to ask the same question of the tests, however. I'll make sure both are covered explicitly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very cool.
Addresses bottom scroll indicator placement when footer is large enough to scroll. Scroll indicator drops down to bottom of table when body is fully scrolled and obscured footer rows begin to scroll into view. Docs updated to show this example.
Note the border rendering issues with the sticky footer cells. I double-checked, and this is existing behavior. Looks to be related to #771.