react-table-library
aria-practices
react-table-library | aria-practices | |
---|---|---|
12 | 4 | |
714 | 1,159 | |
1.7% | 0.9% | |
2.7 | 8.0 | |
2 days ago | 1 day ago | |
JavaScript | HTML | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
react-table-library
-
How to solve overfetching with tRPC APIs when rendering tables (Pt. 1)
I'll use React Table Library for the UI, but this pattern can work with most other tables or datagrids in a very similar way.
-
React datagrid libraries
Maybe give https://react-table-library.com/ a try :)
-
To people who use Chakra-UI in production, what solutions do you use for date pickers, tables, etc?
Perhaps react-table-library with its Chakra UI integration is worth a try!
-
I built a table library for React, would love some feedback
Ah okay. Yes, I didn't link those yet. But essentially you can find all the features on the Features section over here https://react-table-library.com/
-
AntD vs MaterialUI? what do you prefer and why?
https://tanstack.com/table/v8 https://react-table-library.com/
-
Best React Inline Editable Grid?
You could give react-table-library a shot :) The table cells are fully in your control, so you could just use an input field in them.
-
React Tree View for Json object?
Check out this table's tree feature: https://react-table-library.com/
- Show HN: React-Table-Library
-
Chakra UI vs Mantine
If someone is looking for a fully-featured table library that can use either Chakra or Mantine as theme, check out this library.
-
React Arborist – A full-featured tree component for React
FWIW I am working on such a table library for React [0] which has a great tree plug-in. So you can use it either as tree table or tree list (if just having one column).
[0] https://react-table-library.com/
aria-practices
-
Here are the 10 projects I am contributing to over the next 6 months. Share yours
W3C Aria Practices
-
React Arborist – A full-featured tree component for React
I should apologize off-the-bat for not digging in too deeply, but how does this handle keyboard and screenreader accessibility?
W3C has some in-depth list of expected keyboard interactions, though I'm not sure how complete they are:
https://w3c.github.io/aria-practices/#TreeView
https://w3c.github.io/aria-practices/examples/treeview/treev...
I ask because I've tried to implement a [TreeGrid](https://w3c.github.io/aria-practices/#treegrid) myself before and... it's a lot of work. I'd love an accessible, keyboard-friendly React tree :).
-
Custom JavaScript controls can't capture the nuance of form fields (2021)
Yep I totally agree with this.
There are however a bunch of ARIA tags & best practices etc (https://w3c.github.io/aria-practices/) that exist to make popups and dialogs (and other things e.g. tree views or "email-inbox-style" "treegrids" etc) accessible (if implemented correctly).
I am conflicted about these - it is nice that there are ARIA tags for this, but it would also be nice if browsers "understood" aria tags and added some default behaviors (e.g. keyboard navigation). As it is, ARIA tags are essentially "pointless" to anyone who doesn't use an assistive technology, and so non-assitive-technology users nor developers benefit from using ARIA tags so they are often forgotten. If the browsers saw that there was an A11y-tree that matched a treeview or a treegrid, it would be really really nice if they applied some default common keyboard navigation implementation, rather than do nothing and leave it up to the developer to decide what keys do what on each and every site. .... Or on the other hand, is that too prescriptive and should we give developers and UX designers more leeway to design something better, rather than rely on browser-enforced defaults? I guess we are happy with browser defaults for basic inputs, but would we be for a treegrid?
-
4 takeaways from axe-con 2021
The ARIA practices GitHub is a good resource to see where certain patterns fall short.
What are some alternatives?
material-table - Datatable for React based on material-ui's table with additional features
react-arborist - The complete tree view component for React
react-data-table - A responsive table library with built-in sorting, pagination, selection, expandable rows, and customizable styling.
bootstrap-select - :rocket: The jQuery plugin that brings select elements into the 21st century with intuitive multiselection, searching, and much more.
react-table - 🤖 Headless UI for building powerful tables & datagrids for TS/JS - React-Table, Vue-Table, Solid-Table, Svelte-Table
standards-support - Contains documentation for Vispero software support of Web standards
KendoReact Grid - Issue tracker - KendoReact http://www.telerik.com/kendo-react-ui/
monaco-tree - Curiosity hacks with Monaco Editor's tree component
DevExtreme React Grid - Business React components for Bootstrap and Material-UI
aktenkoffer - 💼 Personal document management made easy.
axe-core - Accessibility engine for automated Web UI testing