View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0021132 | MMW 5 | Playlists (Auto) / Search / Filters | public | 2024-08-04 02:32 | 2024-12-19 09:44 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 2024.0 | ||||
| Target Version | 2024.1 | Fixed in Version | 2024.1 | ||
| Summary | 0021132: Keyboard navigation of the tree breaks contextual search persistence | ||||
| Description | If the user navigates to a node that has a persistent contextual search, it breaks contextual search persistence for the current and all future contextual searches. As to the question raised at 0021088 of whether contextual search persistence is desirable or not, we previously decided that it _is_ desirable at 0013612:0046225 . I'm a bit doubtful of that decision, but now's not the time to start making changes. | ||||
| Additional Information | 1 Click Music > All files [List] 2 Type 'beat' ENTER 3 Click Music > Albums [Grid] 4 Click Music > Genres [Grid] 5 Click Music > All files [List] ---> Search persists as expected 6 Click Music > Albums [Grid] 7 Press ALT RIGHT-ARROW --> Focus shifts to the Music > Genres [Grid] view 8 Press SHIFT-TAB 2x in order to move focus back to the Music > Genres node 9 Press ARROW UP 2x in order to move focus to the Music > All files [List] --> Persistence of the contextual search term is lost! --> From this point on any attempts to use contextual search on the node result in no persistence of the search term! | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 3100 | ||||
|
|
The search persistence has been implemented after return to view (i.e. Back) i.e. whenever you use 'Back' (Alt+Left, Backspace, Back button) then the search term is restored for the corresponding navigation history item. In your scenario you clicked the 'All files' again (or used arrow in the media tree) which created _new_ navigation item for which no search has been performed so there was nothing to restore for the new items.. I would say this is expected, but I understand that it is inconsistent with the "funnel" filtering where the "funnel" filter remains active for all nodes under the given collection.. Possible solutions: A) Leave it as is (can result in confusion like yours) B) Get rid of contextual search persistence (probably preferred?) C) Unify it with "funnel" filtering persistence to be persistent for all nodes under the given collection |
|
|
I'm leaning towards B), but agree that we should only make this change at the beginning of another beta cycle. |
|
|
Fixed in 3100 |
|
|
Verified 3100 works as suggested in B) |
