-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[UI] Table Data-Grid #1357
Comments
+1 |
8 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+100 |
+1 |
4 similar comments
+1 |
+1 |
+1 |
+1 |
🙌 💥 +9000 |
+1 |
6 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
@jlukic - Is this on the roadmap at all? |
@tcigrand I'm corralling new component requests. This is actually higher up on the list for me than most component suggestions, however is a lot to implement. |
+1 |
1 similar comment
+1 |
+1 |
5 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
Please use the GitHub Reactions to vote https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments instead of posting |
+1 |
As a first-time semantic ui user, I naively assumed sticky would work this way and the note in docs kinda implies it will. Howsabout a big "this doesn't work with |
Is there any news about this topic? Would be nice to have this implemented in semantic |
+1 |
3 similar comments
+1 |
+1 |
+1 |
Have you seen this? It's not the ideal, but do the job! |
@brunotourinho Are you referring to the pagination? |
@zykadelic yep! it's a pretty nice component! |
Another data-table implementation using Semantic UI: |
+1 |
+1 |
1 similar comment
+1 |
I often have many rows of data to present to the user - more than will fit on the screen. It makes it quite difficult for the user if they have to scroll up from the current row they are looking at in order to see the column headers to know what the data is.
I have ways in which to make this work that involve quite a bit of custom JS and CSS, but it would be much nicer if Semantic-UI provided a "fixed header" class to the table.
The text was updated successfully, but these errors were encountered: