4 ms·
No reason to sacrifice accessibility and styling in the name of performance: https://github.com/jpmorganchase/regular-table https://github.com/jpmorganchase/reg
by timkpaine 5y ago
No reason to sacrifice accessibility and styling in the name of performance: https://github.com/jpmorganchase/regular-table https://github.com/jpmorganchase/regular-table
- noduerme 5y agoFunny. I just rolled my own datagrid for a portion of a larger application that already uses DataTables for various stuff. I wanted something that acted like this, was fast and allowed for easier row and column styling (including in the data itself). Also, faster and more flexible animated resizing. I ended up using CSS grid divs and without any virtualization on my part, they're shockingly performant. Both Chrome and FF easily handle 1m cels which is more than my use case will ever need. They're really quick at blitting just the necessary cells, making it wayyy smoother than DataTables in virtual mode. And anything on an actual canvas tag...? forget about it.
- jassmith87 5y agoGlide Data Grid has a fully accessible DOM subtree. No need to sacrifice accessibility just to use a canvas. Come on, its 2022 we have the tools. What makes Canvas even nicer is I can export a subdom that is bespoke for screen readers. It is exactly what the screen readers want, nothing more, nothing less. It works wonderfully. Disclosure: I am the primary developer of Glide Data Grid.