[MGNLUI-459] As a user I can use search and it works smooth and consistently so that I can use it for navigation in large content Created: 21/Dec/12 Updated: 10/Mar/21 Resolved: 10/Mar/21 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | app framework |
| Affects Version/s: | 5.0 |
| Fix Version/s: | None |
| Type: | Story | Priority: | Major |
| Reporter: | Andreas Weder | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | framework, frontend, search, ux | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Release notes required: |
Yes
|
||||||||
| Description |
|
While search does work to some extend, it currently exhibits a number of rough edges and in general doesn't seems to work as currently specified. We should either clean up the way it works now or change it so it works as designed on the Basic Search concept page. Currently, if I move the cursor into the search field (making it white), the content area below changes and shows a list of items I can then filter by using a search term. But Basic search in Magnolia has been redefined to work as filter on the existing view. If I'm in thumbs view, it filters the thumbs. If I'm in list view, it filters the list of items shown there. The advantage of this is mainly that I can switch between views to show search results in different ways. Basic search on views is described here: http://wiki.magnolia-cms.com/display/UX/Basic+search+in+apps As for trees, search there is quite a bit more complicated to implement. If we have to cut things short, I would be fine, if we:
Before you start working on this, please confirm with Philipp and me whether we really want to have this for 5.0 (or for a later release). We could:
|