View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0015251 | MMW 5 | Playlists (Auto) / Search / Filters | public | 2018-12-11 23:04 | 2019-01-11 16:19 |
| Reporter | rusty | Assigned To | |||
| Priority | high | Severity | major | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 5.0 | ||||
| Target Version | 5.0 | ||||
| Summary | 0015251: Contextual search doesn't work on main nodes (home / music / etc) - when 'scroll to matches' choice is selected | ||||
| Description | I'm not sure when this issue was introduced, but contextual search is no longer working on the various main nodes. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
For me it still works: https://www.dropbox.com/s/n91jb0yt78hxfs8/Screenshot%202018-12-12%2010.54.36.png?dl=0 Are you sure that you have the default choice "filter matches" here: https://www.dropbox.com/s/nynb5osw9efdyq9/Screenshot%202018-12-12%2010.56.16.png?dl=0 ? Just note that contextual search for the main collection nodes was suggested to work more like global search. i.e. it works similar like the global search, but content is limited to the current collection. |
|
|
I thought we'd already discussed this in a bug, but can't seem to find where: in views that represent more tracks than are represented in the view (e.g. Browser view of Home, Music, Classical, Podcasts, etc. (i.e. Home + all Collection nodes)) it never makes sense to 'scroll to match' since doing so almost always shows nothing! I guess what I'm saying is that just as it always makes sense to 'scroll to match' for Now Playing, it always makes sense to filter matches for the views described above. What do you think? Are there any other views to which this logic should apply? |
|
|
I would say that it always makes sense to perform "scroll to matches" when configured so. e.g. user can have a large pinned list (that is shown on the home/collection views) and want to scroll to a concrete pinned item In addition user can always use Crtl+F to perform a search. |
|
|
OK--thanks. I hadn't thought of that usecase for the Home node, but you're probably right. As to the Collections nodes (which don't yet support pinned content), CTRL-F works. Resolving. |
