This is actually by design - if you activate grouping for a field, Composite C1 will sort those grouping folders for you (ascending by default, descending if you explicitly set it on the grouping field). Then - once you open such a grouping folder, the elements in there will be sorted as you asked for.
The reason is simply that the alternative makes no real sense. As an example, take the data below and tell me what would be the correct order for the grouping folders?
PageId GroupName LocalOrdering
page1 group1 1
page2 group2 2
page3 group1 3
page4 group2 1
page5 group1 2
page6 group2 3
The problem here is that you have two grouping folders, and the field you would sort by say 1, 2 and 3 for both group1 and group2. So which is first, group1 or group2?
Here I opted for the route of "least surprise" from an end-user point of view - that a list of folders grouping data is always sorted. I hope you'll agree this makes good sense.
The reason is simply that the alternative makes no real sense. As an example, take the data below and tell me what would be the correct order for the grouping folders?
PageId GroupName LocalOrdering
page1 group1 1
page2 group2 2
page3 group1 3
page4 group2 1
page5 group1 2
page6 group2 3
The problem here is that you have two grouping folders, and the field you would sort by say 1, 2 and 3 for both group1 and group2. So which is first, group1 or group2?
Here I opted for the route of "least surprise" from an end-user point of view - that a list of folders grouping data is always sorted. I hope you'll agree this makes good sense.