View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0019457 | MMW 5 | Playlists (Auto) / Search / Filters | public | 2022-10-12 13:19 | 2024-07-31 23:14 |
| Reporter | Ludek | Assigned To | |||
| Priority | urgent | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | reopened | ||
| Product Version | 5.0 | ||||
| Target Version | 5.1 | Fixed in Version | 5.1 | ||
| Summary | 0019457: Enhance 'Scroll to match' options | ||||
| Description | Originally mentioned in 0017058:0060095 : Currently 'Scroll to match' scrolls based on primary sort field (power scroll), but that's not obvious from the UI ( + can be confusing and not desired). The suggestion is to enhance the current: Filter matches, Scroll to match => Filter matches, Scroll to match (primary sort field), Scroll to match (all displayed fields) | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2826 | ||||
|
|
Implemented in 5.1.0.2800 |
|
|
Verified 2803 |
|
|
The configuration for this option has been implemented in the contextual search options, but hasn't been implemented in Options > Search ! |
|
|
Fixed in 2826 |
|
|
Works as expected on 2826. One small issue is the Playing which is sorted on # by default (and no column with shuffle), which means 'primary sort field' shouldn't find anything but numbers. Instead it works as 'all fields'. I'd recommend setting it to 'all fields' by default for Playing and Playlists as the default sort column is #, independent of what it's set for other nodes. Keeping 'primary sort field' still makes sense as user can sort on a column and may then want to use this. |
|
|
ok, I agree that # should search all fields.. Fixed in 2827 |
|
|
Verified 2827 |
|
|
When setting to all fields it doesn't jump to Genre values matching the query. When sorting on Genre and setting it to primary sort, it does work as expected. |
|
|
For me it jumps to genre in both cases and also by code revision I don't see an issue.. Couldn't it be a test error? |
|
|
It works now, this was likely caused by 0021124. |
