Appears on 2.1_M.1.RC1: 3d2c0f5902cacf9d8544bf263b51ef0dd1a7218c Step to reproduce: 1. Enter a project page 2. Go to Image recipes or software recipes 3. Sort the table by layer 4. From Edit columns hide layer column Expected result: Revert the sorting to the default sorting (i.e. "Recipe") Observed result: Table is sort by default column but the column is not bold and the arrow is missing. If you check the layer column again the default sorting remains but the "layer" appears bold.
This behavior appears also in all project builds table.
See also bug 7198, which is related.
See also bug 8791, which is related.
Belen tested a previous version of my patches for this, with the following result: So, tested this across Toaster (if a table is not on the list, it means the bug doesn't apply because either only one column is sortable, or because none of the sortable columns can be hidden using the 'edit columns' menu). It seems to work in all the tables implemented with ToasterTable * Image recipes * Image recipe details (packages included) * Custom image recipe details (add | remove packages) * Software recipes * Machines * Layers * All builds * Project builds If the scope of the patch is only tables implemented with ToasterTable, then this is good to go. For the sake of completion, this is working in the following tables *not* implemented with ToasterTable * Recipes * Packages It doesn't seem to work in the following tables *not* implemented with ToasterTable * Packages included * Tasks (and by extension Time, CPU time and disk I/O since they are the same as the tasks table).
Now fixed for all cases; see https://lists.yoctoproject.org/pipermail/toaster/2016-March/004329.html for review request.
Now in bitbake master.
I can still reproduce it for All builds table and Project builds table. Fixed for Image recipes table and Software recipes table.
Sent another patch to mailing list: https://lists.yoctoproject.org/pipermail/toaster/2016-April/004490.html
Last patch didn't make it to 2.1, so moving this bug to 2.2M1
*** Bug 7198 has been marked as a duplicate of this bug. ***