[MGNLUI-6478] Remove slide down animation (to be validated) Created: 22/Dec/20  Updated: 25/May/23  Resolved: 25/May/23

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Anja von Gunten Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screenshot 2021-01-07 at 09.50.04.png     PNG File Screenshot 2021-01-07 at 09.50.14.png     PNG File Screenshot 2021-01-07 at 09.50.20.png    
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)
Date of First Response:
Epic Link: Full-Text Search (FTS) within Apps

 Description   

1) Animations

To be reviewed:
_As the user will switch btw ‘All content’ and ‘Apps’ the slide down animation do not make sense anymore

  • Remove the slide down animations all together
  • Also for Apps, Tasks, Notifs_

  • When in an app, no slide down as search will happen on the actual app's view
  • Should we slide the app down as today when switching to "All" search? Case:
    • Search term, switch to all
    • Result not on list
    • User wants to go back to previous app - two options:
      • As today (minimized app at the bottom to go back)
      • After removal of slide down/minimizing: clear search term and switch back to app using app switcher (seems more complicated, removes the quick 'back to where I was')
  • How about tasks & notifications? Slide-down and minimize is a known pattern by now.

2) Click targets 

As we remove 'slide down' the small arrows in Tasks, Notifs are not appropriate anymore.

Also good opportunity to improve size of click target

  • Remove the arrows
  • Implement click target / hover style as per mockup

 


Generated at Mon Feb 12 09:36:52 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.