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)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: etienne, Assigned: etienne)

References

Details

Attachments

(1 file, 1 obsolete file)

* 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
Blocks: 838012
Attached patch WIP (obsolete) — Splinter Review
Assignee: nobody → etienne
When you get further along, let's have dkuo do the review on this.
Attached patch Patch proposalSplinter Review
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)
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.
(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.
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.

Attachment

General

Created:
Updated:
Size: