Conversation
|
Visually I think this is a great idea. It's pretty clear which column is primary and which are secondary. In terms of the sort behavior I'm confused though. If I apply a sort to Count, it sorts correctly. Then if I apply a sort to Value1 (a column where each row has the same value) the rows get seemingly randomly scrambled. Even though by my understanding they should still be sorted by Count, because if the primary sort is just an arbitrary order if the values are the same, the rows should be in the order of the secondary sort column, right? I'm seeing the same thing in both the gif and testing it out myself. |
|
Indeed, if all the values are the same in the primary column, the rows should be sorted along the secondary column. If not, it's a bug! Note that in this example, the columns Value1, Value2 and Value3 contain random integers between 0 and 100 |
|
Ok, good to know! I thought I was going crazy for a second. It's not really related to the styling changes here. So I'll approve this and open an bug. |
fixes #93
Use the
aria-posinsetattribute to style the column header depending on its sort orderScreencast.From.2025-04-08.11-59-24.webm.mp4