Bug 6061

Summary: In the installed packages table, sorting by 'size' also sorts by 'size over total' (and vice versa)
Product: [Build System, Metadata & Runtime] Toaster Reporter: Belen Barros Pena <belen.barros.pena>
Component: toasterAssignee: Dave Lerner <dave.lerner>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: alexandru.damian, belen.barros.pena, cristiana.voicu, david.reyna, jessica.zhang
Version: unspecified   
Target Milestone: 1.6 M5   
Hardware: All   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
2 sorted columns none

Description Belen Barros Pena 2014-03-28 10:11:47 UTC 
Created attachment 1864 [details]
2 sorted columns

Tables should only have one sorting criteria applied at any given time (i.e. only one column heading should have the .sorted class applied). However, in the installed packages table, sorting by "Size" or "Size over total" will apply the .sorted class to both "Size" and "Size over total" (see attached screenshot).

This should not happen: only the heading I clicked should take the .sorted class
Comment 1 Dave Lerner 2014-03-28 14:43:43 UTC 
Table columns Size and Size over total are not independent.  Sorting by Size is the same as sorting by Size over total. This should be made clear to the user that these two columns are in fact dependent, sort together and can not be sorted separately, correct?
Comment 2 Dave Lerner 2014-03-28 14:51:56 UTC 
On further consideration, I agree with the original defect.  It doesn't make sense to have views that show both columns selected as being sorted. Bug accepted.
Comment 3 David Reyna 2014-04-09 23:16:05 UTC 
commit 4b17947f24987a2523239c06d4aeea596587c76c
Comment 4 Belen Barros Pena 2014-04-10 18:08:22 UTC 
verified in master:863cc7483f5ee43189537940de8ee5c0964d24cc