Bug 4173 - Tables keep state but search query is gone: if we remember table state, the search query should display
Summary: Tables keep state but search query is gone: if we remember table state, the s...
Status: VERIFIED FIXED
Alias: None
Product: Hob
Classification: Build System, Metadata & Runtime
Component: hob (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Undecided normal
Target Milestone: ---
Assignee: Cristiana Voicu
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-04-02 17:23 UTC by Belen Barros Pena
Modified: 2013-04-03 10:43 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments
state-without-search-query.png (32.69 KB, image/png)
2013-04-02 17:23 UTC, Belen Barros Pena
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Belen Barros Pena 2013-04-02 17:23:58 UTC
Created attachment 1148 [details]
state-without-search-query.png

Steps to reproduce:

1. Launch Hob
2. Select a machine (eg. atom-pc) and a base image (e.g. core-image-sato).
3. Click "Edit recipes"
4. Enter a search query in the "Included recipes" tab (e.g. tel)
5. Navigate to the "All recipes" tab
6. Navigate back to the "Included recipes" tab

Outcome: the table remembers its last state (only one recipe displayed matching the search query 'tel'), but the search query itself no longer shows in the search box. The result is pretty odd: you have no feedback as to the reason why only one recipe is displayed in the tab (screenshot attached).

Expected outcome: if we remember the table state (which I think we should until users either cancel or proceed to the next step), the search query must also show in the search box.
Comment 1 Belen Barros Pena 2013-04-02 17:24:37 UTC
Cristiana: I hope it's ok if I assign this to you.

Thanks!
Comment 2 Cristiana Voicu 2013-04-03 07:06:52 UTC
Hi Belen,

I have fixed this within the commit 0d47a7d8e8b50fbf0ed6ec8f3a8b95a11c067804, can you please check if it is ok as it is?
Thanks,
Cristiana
Comment 3 Belen Barros Pena 2013-04-03 10:43:22 UTC
It looks like this has been fixed by no longer remembering the table state. That's fine by me: at least there is no confusion as to what's happening.
Comment 4 Belen Barros Pena 2013-04-03 10:43:43 UTC
Verified on fd4e5c6c58183f1a017c6b5fe4d43c320e273567