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

Consider supporting virtualization with CSS Grid #124

Open
inokawa opened this issue Jul 16, 2023 · 6 comments · May be fixed by #204
Open

Consider supporting virtualization with CSS Grid #124

inokawa opened this issue Jul 16, 2023 · 6 comments · May be fixed by #204

Comments

@inokawa
Copy link
Owner

inokawa commented Jul 16, 2023

No description provided.

@inokawa
Copy link
Owner Author

inokawa commented Jul 20, 2023

@inokawa inokawa linked a pull request Oct 8, 2023 that will close this issue
@inokawa inokawa self-assigned this Jul 7, 2024
@inokawa inokawa removed their assignment Oct 12, 2024
@inokawa
Copy link
Owner Author

inokawa commented Nov 20, 2024

@szszoke
Copy link

szszoke commented Dec 16, 2024

Do you have any specific plans/goals with this? I'm just curious.

Would this be an internal implementation detail or are you planning on exposing things to the consumers of the grid as well?

I.e. set column count with repeat(auto-fit, ...)/ repeat(auto-fill, ...).

@inokawa
Copy link
Owner Author

inokawa commented Dec 17, 2024

There is an old and rough implementation in #204 but there is no clear schedule for now.

When I was working on list virtualization, I had noticed grid virtualization was very different from list virtualization. Its cell sizes are usually fixed by its columns/rows, and it has different usecases like data-grid, spreadsheet, masonry, and so on. CSS grid is flexible enough to support them so I want to use it.

@AlejandroAkbal
Copy link

Would love to see this implemented, currently using TanStack Virtual for Vue 3 to get a virtualized masonry grid, but they only support vertical gap, not horizontal gap, which makes the designs ugly and impossible to use :/

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.

3 participants