Closed
Bug 1016231
Opened 10 years ago
Closed 10 years ago
[Collections App] Collection open/close transitions
Categories
(Firefox OS Graveyard :: Gaia, defect)
Tracking
(feature-b2g:2.0, tracking-b2g:backlog)
People
(Reporter: amirn, Unassigned)
References
Details
(Whiteboard: [systemsfe])
No description provided.
Reporter | ||
Updated•10 years ago
|
Blocks: collection-app
Depends on: 1016230
Updated•10 years ago
|
blocking-b2g: --- → backlog
feature-b2g: --- → 2.0
Whiteboard: [systemsfe]
Reporter | ||
Comment 1•10 years ago
|
||
Ran, can you take this?
Comment 2•10 years ago
|
||
From v1.3, Collections are animated in with a transition that resembled Marketplace app's transition (Bug #924764). Now that Collections open out of Homescreen process in a separate app, it's not possible to mimic the transition. Out of the box, Collections can transition in either by "grow" or "slide up". IMO, giving it an "app transition" would make it feel less of a homescreen feature. Still, knowing that we're short on time, we can settle on it. Peter, could you refer this to UX?
Flags: needinfo?(pdolanjski)
Comment 3•10 years ago
|
||
As per bug 1016230, we agree that the current transition conflicts with the planned notifications transition. As a result, we are proposing a quick (300 ms) fade in. Please flag me if you need this spec'd out or if you need alternatives.
Flags: needinfo?(pdolanjski)
Comment 4•10 years ago
|
||
Sorry, something I forgot to clarify during today's standup - We will not have notifications from the bottom in 2.0. So, is this custom transition something we will need in 2.0, or can it be 2.1? Are we ok with a simple slide from the bottom for collections in 2.0?
Flags: needinfo?(rmacdonald)
Flags: needinfo?(jachen)
Comment 5•10 years ago
|
||
Notifications aside, it still seems a bit awkward as a transition in general so we were hoping it could be changed in 2.0.
Flags: needinfo?(rmacdonald)
Flags: needinfo?(jachen)
Updated•10 years ago
|
Target Milestone: --- → 2.0 S3 (6june)
Updated•10 years ago
|
Target Milestone: 2.0 S3 (6june) → 2.0 S4 (20june)
Comment 6•10 years ago
|
||
Now that bug 1021510 has landed, we perform a fade-in/fade-out of all activities. In this case I don't think that it makes sense to copy the current production transition. I think we are able to do something interesting if we would want to - but we should definitely get some UX specs/eyes on it. I'm going to close this as a duplicate of bug 1021510 for tracking purposes, but please let me know if you guys disagree with this, or have something immediately actionable.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•9 years ago
|
blocking-b2g: backlog → ---
tracking-b2g:
--- → backlog
You need to log in
before you can comment on or make changes to this bug.
Description
•