Closed
Bug 981052
Opened 10 years ago
Closed 10 years ago
[Messages] We should ask for confirmation when the user tries to delete an outgoing message
Categories
(Firefox OS Graveyard :: Gaia::SMS, defect)
Tracking
(tracking-b2g:backlog, b2g-v2.2 fixed)
Tracking | Status | |
---|---|---|
b2g-v2.2 | --- | fixed |
People
(Reporter: julienw, Assigned: jorgep)
References
Details
Attachments
(1 file)
From Ayman in Bug 976495 comment 15: However from what i can see I would propose that there is a hole in the current UX. I would suggest that the path for deleting and outgoing message whether sending, sent or failed should be the following: **PATH** 1) open message app 2) select either to compose a new message or an existing message thread 3) compose a message 4) select send 5) long press on the outgoing message (irrespective of state it is in, means any outgoing message even if it's sent a long time ago) 6) select ‘delete’ **EXPECTED** the user is presented with a ‘confirm deletion’ screen before message is deleted. This screen should existed to catch the instance that the user has select delete by mistake. I would propose deletion screen should have the following structure: <BODY>Delete selected message?</BODY> <CTAs>Cancel | OK </CTAs> Selecting ‘Cancel’ takes the user back to the message thread Selecting ‘OK’ deletes the selected message and: if the message thread still contains other messages returns the user back to the message thread with the if the message thread no longer contains other messages returns the user back to the message inbox **ACTUAL** if the message thread still contains other messages returns the user back to the message thread with the if the message thread no longer contains other messages returns the user back to the message inbox Needinfo Joe to put this in backlog.
Flags: needinfo?(jcheng)
Assignee | ||
Updated•10 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → jpruden92
Assignee | ||
Comment 2•10 years ago
|
||
Attachment #8482202 -
Flags: review?(schung)
Comment 3•10 years ago
|
||
Comment on attachment 8482202 [details]
23565.html
Hi Jorge, thanks for the contribution, just a small nit on github and please request review again when you are ready, thanks!
Attachment #8482202 -
Flags: review?(schung)
Assignee | ||
Updated•10 years ago
|
Attachment #8482202 -
Flags: review?(schung)
Assignee | ||
Comment 4•10 years ago
|
||
I've already done the change. Thanks!
Comment 5•10 years ago
|
||
(In reply to Jorge Prudencio [:jorgep] from comment #4) > I've already done the change. Thanks! Ah, sorry for the misleading. Please see the comment on github and update the patch again, thanks.
Assignee | ||
Comment 6•10 years ago
|
||
Hello Steve, I've already done the change. Thanks!
Flags: needinfo?(schung)
Comment 7•10 years ago
|
||
Comment on attachment 8482202 [details]
23565.html
r=me, thanks for the helping!
Attachment #8482202 -
Flags: review?(schung) → review+
Flags: needinfo?(schung)
Comment 8•10 years ago
|
||
In master : b2aaec7bfda8d4573ea96c4370a694fe646e7e57
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
status-b2g-v2.2:
--- → fixed
Target Milestone: --- → 2.1 S4 (12sep)
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
•