Right now the cookie we have in place to keep state of Toaster tables seems to cover only the Edit columns menu (which columns are shown and which hidden). We should probably cover all other elements as well, which include: * The number selected in the 'Show rows' dropdown menu * The sorting applied * The page number I was in * A filter applied * A search query performed So if in the All builds table I select to see only Today's builds by applying a filter in the Completed on column, and then click on a build, when I return to the All builds table the filter will still be applied.
On second thoughts, this might not be such a good idea. Let's not touch it for the moment.
Sorry for all the back and forth with this one. We should probably keep * the "Show rows" selection * the sorting applied Otherwise, it resets every time, which is a bit maddening.
A patch to remember the number of rows across searches in the same page has been submitted for review on poky-contrib/adamian/20140408-tables-5878 Proposing that the feature about remembering the sorting and the number-of-rows across sessions (e.g. browser closing and re-opening) be moved for 1.7.
(In reply to comment #3) > A patch to remember the number of rows across searches in the same page has > been submitted for review on poky-contrib/adamian/20140408-tables-5878 This seems to be working: "Show rows" selection is kept when I search(although not between pages or sessions). > > Proposing that the feature about remembering the sorting and the > number-of-rows across sessions (e.g. browser closing and re-opening) be > moved for 1.7. Done: bug 6126
merged to master http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=b14482ef611d166b5f158cede371f73c26e2a937
Number of rows resets to page default (25 for tasks, 100 for recipes and packages) when pressing the search button. Tested on master branch 8b7116d25ed6255a03895d835e5a0560858ab496 Fedora 20 OS Firefox 31.0 browser
Rescheduling.
Rescheduled for M4, this is not an enhancement, but a normal bug.
The functionality added with bug 6126 covers the request here. It does not work across browser sessions, but it does within the same session across pages and searches, which is good enough. Setting this bug as duplicate. *** This bug has been marked as a duplicate of bug 6126 ***