View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0018648 | MMW 5 | Main Panel: Toolbars & Menus | public | 2021-12-09 02:01 | 2024-08-29 04:47 |
| Reporter | barrym | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | feedback | Resolution | open | ||
| Platform | Windows | OS | - | OS Version | 10 |
| Product Version | 5.0 | ||||
| Target Version | 5.1 | ||||
| Summary | 0018648: Unable to efficiently browse search history in Contextual search box | ||||
| Description | In the forum Ludek asked why the auto-close-when empty behaviour of the Contextual Search control is unhelpful. Due to Forum traffic I don't know whether he saw my answer. The problem is that, unlike in the Global search control, we cannot navigate back through recent search items easily in the Contextual Search box. From my forum post: The dropdown is only available after I have typed one or more characters. If I am trying to remember something from another time, in a Contextual Search< I have to give you a letter, and I have guessed the wrong letter, I backspace so I can try another, ==> and you close the search control. It is like trying to go get my groceries inside in a gale. Every time I pick up the groceries, the bloody wind slams the door shut. ===> Couldn't you close the control when focus is moved elsewhere, rather than when the search string is empty? | ||||
| Steps To Reproduce | https://www.mediamonkey.com/forum/viewtopic.php?f=33&t=100813 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
I think that the current need to remember at least first letter is a minor limitation IMO. As for the suggestion to not close the control when the search string gets empty. My feeling is that it would be rather a downside -- i.e. the need to perform one more step to close the empty control. Assigned to Rusty to triage. |
|
|
I think that 0021088 is the most severe aspect of the workflow, and suspect that the need for the change suggested here will be mitigated by that fix. To be reviewed again after 0021088 is fixed. |
