2 ms·
Perhaps my tone was a bit harsh, but the examples aren't even rendering properly on iOS. Compared to desktop, it's chopping off entire columns, and you can only
by bdcravens 7y ago
Perhaps my tone was a bit harsh, but the examples aren't even rendering properly on iOS. Compared to desktop, it's chopping off entire columns, and you can only scroll horizontally via the header, not the body of the table. Additionally, there's no scroll bar to indicate the missing columns: I only knew they were there by comparing side-by-side with the desktop site.
So yes, the responsiveness of the component is consistent with the responsiveness of the documentation site, and as I expected, the component doesn't "look really good" on mobile. After bothering looking at it, I'll consider this component the next time I build a desktop-only application.
- liteneo 7y agoI'm sorry I forget to mention the component is designed for desktop app only, I think a table component could be in a completely different look and interactions Besides, I'm the only one right now to create and maintain the component, and so does the website, so I don't have enough time to polish the experience of the website on mobile
- bdcravens 7y agoThanks, that clears it up. Honestly no reason to worry the doc site is it's only intended for desktop; consider it a support filter. :-)