834333 - [META] [Transitions. UX] Implement transitions as specified.

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: Gaia::E-Mail, defect)

Description

[Victoria Gerchinhoren [:vicky]]

Lack of Transitions affect the experience. Required for TEF build.

Transitions a key feature to give the user a clue of the architecture of the OS and how to navigate it.

Please refer to specs: 
https://www.dropbox.com/sh/ekzrrz7um4uj6y0/NVzqB1D4hx/03%20Transitions
TransitionsVXX.pdf (latest version)

Comment 1

[Andrew Sutherland [:asuth] (he/him)]

Please call out specific transitions that you do need believe are implemented, especially since where you may think we haven't implemented a transition, it may be implemented but experiencing platform issues.  For example. you filed bug 818081 on the inbox->message transition which was already implemented at the time of filing, but was not animating super well.  I'm going to mark that WFM now since I believe we have improved that in bug 828266.

The other outstanding transition bug we have is:
Bug 809791 - [UX VD] Drawer. Folder List/horizontal stripes Menu button in orange header is wrong, does not animate/transition correctly when tray is displayed

Comment 2

[Victoria Gerchinhoren [:vicky]]

Andrew, I will specify the individual transitions and convert this one into a meta bug, as I have to do it with every transition of each app. 

The transition you mention of going deeper is not well implemented, is not a whole block that moves to the left, please read specs carefully, the header animates at a different time, we're on the process of having all transitions implemented in CSS so you can have all easily and consistend along the whole OS. You can grab the code for this "Going deeper" one here: 
http://buildingfirefoxos.com/transitions.html#deeper

Comment 3

[Andrew Sutherland [:asuth] (he/him)]

Thank you for clarifying what was wrong with going deeper and providing a link to the CSS demonstration!  When you filed bug 818081 with the comment "See page 11 of the transitions spec doc", it was not immediately clear what was wrong with our implementation so I assumed you were experiencing what I was also seeing.

Are there any other variations on the demo page, such as one that uses discrete DOM nodes instead of image slices, or can be seen as a full-page demo on the phone?  I'm a little concerned about whether our platform can currently accelerate that example without hitching.

Comment 5

[Rafael Rebolleda]

My mistake, ignore the dupe comment above.

Comment 6

[Victoria Gerchinhoren [:vicky]]

Updated link to the transitions specs:
https://www.dropbox.com/sh/tsns9vgbgzuefx1/is0W_IeHkB

Some folders were moved, sorry for that.

Comment 7

[Andrew Sutherland [:asuth] (he/him)]

Dependent bugs are all resolved, closing meta bug.