You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Scroll down to the table sample for Sort, and the md-sort property is set to Name, as indicated by the arrow adjacent to the Name column header.
The data however is unsorted (the sequence being IDs 1,2,3,4,5 as in the underlying dataset). Click the column header to actually apply a sort by Name.
Thus the md-sort property is only enabling the sort facility, but on first load, whilst the directional arrow is drawn to indicate that the data is being sorted, the data is not actually sorted until the column header is clicked, rather it remains unsorted and is displayed in the same sequence as it exists in the underlying array.
Screenshot for clarity.
This is using 1.0.0-beta-10.2.
This is my first time raising an issue, apologies if I have got anything wrong and my huge thanks to all involved for their great work.
The text was updated successfully, but these errors were encountered:
VdustR
changed the title
md-sort not applied on initial render of md-table
[MdTable] md-sort not applied on initial render
May 23, 2018
Given the following example: https://vuematerial.io/components/table/
Scroll down to the table sample for Sort, and the md-sort property is set to Name, as indicated by the arrow adjacent to the Name column header.
The data however is unsorted (the sequence being IDs 1,2,3,4,5 as in the underlying dataset). Click the column header to actually apply a sort by Name.
Thus the md-sort property is only enabling the sort facility, but on first load, whilst the directional arrow is drawn to indicate that the data is being sorted, the data is not actually sorted until the column header is clicked, rather it remains unsorted and is displayed in the same sequence as it exists in the underlying array.
Screenshot for clarity.
This is using 1.0.0-beta-10.2.
This is my first time raising an issue, apologies if I have got anything wrong and my huge thanks to all involved for their great work.
The text was updated successfully, but these errors were encountered: