Closed
Bug 851227
Opened 13 years ago
Closed 13 years ago
[email] implement the UI flow for the draft feature
Categories
(Firefox OS Graveyard :: Gaia::E-Mail, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: etienne, Assigned: etienne)
References
Details
Attachments
(1 file, 1 obsolete file)
|
7.25 KB,
patch
|
Details | Diff | Splinter Review |
* The "confirm discard" dialog becomes an action menu with cancel/save/discard options
* When a message in the special Draft folder is clicked, we should open a compose card instead of a message reader card
* The email should be automatically saved on the mozvisibilitychange event when the app goes into the background
| Assignee | ||
Comment 1•13 years ago
|
||
Assignee: nobody → etienne
Comment 2•13 years ago
|
||
When you get further along, let's have dkuo do the review on this.
| Assignee | ||
Comment 3•13 years ago
|
||
The backend isn't ready yet, but since the (empty) methods are already created, the order in which the backend and the frontend land shouldn't matter.
Attachment #725037 -
Attachment is obsolete: true
Attachment #726233 -
Flags: review?(dkuo)
Comment 4•13 years ago
|
||
Etienne, I haven't read the latest UX spec in bug 838012 yet, I will go through it first then back to review this one.
Comment 5•13 years ago
|
||
(In reply to Etienne Segonzac (:etienne) from comment #3)
> The backend isn't ready yet, but since the (empty) methods are already
> created, the order in which the backend and the frontend land shouldn't
> matter.
I think the front-end will need to wait on the back-end for landing since it would be very confusing for us to claim we can save a draft but then not save it.
| Assignee | ||
Comment 6•13 years ago
|
||
Comment on attachment 726233 [details] [diff] [review]
Patch proposal
This landed as part of https://github.com/mozilla-b2g/gaia/commit/85a36ba1a18a9d689565677b3506d5903ccfb0cd
Attachment #726233 -
Flags: review?(dkuo)
| Assignee | ||
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•