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 at the bottom of a Table with ghost cells triggers a "bounce" #3975

Closed
nadia26 opened this issue Feb 21, 2020 · 1 comment
Closed

Comments

@nadia26
Copy link

nadia26 commented Feb 21, 2020

Environment

  • Package version(s): core 3.22.3, table 3.8.3

If possible, link to a minimal repro (fork this code sandbox): https://codesandbox.io/s/blueprintjs-3-playground-4v9h0?fontsize=14&hidenavigation=1&theme=dark

Steps to reproduce

  1. Make a Table with enableGhostCells={true}
  2. Set the table to have more rows than are visible in the table's height. i.e. scrolling is necessary to reach the final row.
  3. Scroll all the way to the bottom of the table.

Actual behavior

A "bounce" effect. When you scroll past the bottom of the table, the scroll bar on the right moves upwards momentarily and then back down to the bottom. This gives the effect that more data is being loaded (and then potentially hidden) when it's not. It looks as if ghost cells are being inserted on scroll, and then removed upon realizing they're not necessary.

Expected behavior

Vertical scrolling looks as it would on the same tables with enableGhostCells={false}

Possible solution

Short of a full solution, the ability to enable ghost cells just horizontally would accomplish what we're looking for.

@adidahiya
Copy link
Contributor

This seems similar to #5027, which has been fixed in recent versions of @blueprintjs/table in the Table2 component. I can't repro it anymore, see this sandbox: https://codesandbox.io/s/great-greider-8mtmkg?file=/src/index.tsx

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

No branches or pull requests

2 participants