Closed
Bug 853752
Opened 12 years ago
Closed 12 years ago
B2G MMS: after retrieving MMS, delete the thread containing the previous notification indication
Categories
(Core :: DOM: Device Interfaces, defect)
Tracking
()
People
(Reporter: airpingu, Assigned: airpingu)
References
Details
Attachments
(2 files, 7 obsolete files)
(deleted),
patch
|
airpingu
:
review+
|
Details | Diff | Splinter Review |
(deleted),
patch
|
vicamo
:
review+
|
Details | Diff | Splinter Review |
When receiving an MMS, we expect to receive 2 types of notification indications. The first one is asking users to retrieve MMS. The second one is the retrieved MMS with the real content and receivers. For now, we're treating these 2 notification indication as 2 different DB records. However, we shouldn't do that because they should belong to different threads. A user scenario could be: one thread collects the "download request" messages and the other collects the real MMS message involved with the receivers. See bug 845643 for the previous implementation.
Assignee | ||
Comment 1•12 years ago
|
||
After some off-line discussions, we decide to change our goal for this issue to: after retrieving MMS (that is, a retrieval confirmation is received), we should delete the thread containing the previous notification indication, if the thread doesn't contain any messages anymore.
Summary: B2G MMS: shouldn't treat the two notification indications as different DB records when receiving MMS → B2G MMS: after retrieving MMS, delete the thread containing the previous notification indication
Comment 2•12 years ago
|
||
Updated•12 years ago
|
Assignee: nobody → ctai
Status: NEW → ASSIGNED
Updated•12 years ago
|
Assignee: ctai → gene.lian
Assignee | ||
Comment 5•12 years ago
|
||
This should also be marked as leo+, because we should delete the notification thread after the MMS is received. Otherwise, we'll have redundant threads referring to the same MMS.
blocking-b2g: --- → leo?
Whiteboard: [NO_UPLIFT]
Assignee | ||
Comment 6•12 years ago
|
||
Attachment #736730 -
Attachment is obsolete: true
Attachment #738441 -
Flags: review?(vyang)
Attachment #738441 -
Flags: review?(ctai)
Updated•12 years ago
|
blocking-b2g: leo? → leo+
status-b2g18:
--- → affected
Assignee | ||
Comment 8•12 years ago
|
||
Attachment #738441 -
Attachment is obsolete: true
Attachment #738441 -
Flags: review?(vyang)
Attachment #738441 -
Flags: review?(ctai)
Attachment #739009 -
Flags: review?(vyang)
Assignee | ||
Updated•12 years ago
|
Attachment #739009 -
Flags: review?(vyang)
Assignee | ||
Comment 9•12 years ago
|
||
Attachment #739009 -
Attachment is obsolete: true
Attachment #739009 -
Flags: review?(vyang)
Attachment #739045 -
Flags: review?(vyang)
Assignee | ||
Comment 10•12 years ago
|
||
Attachment #739045 -
Attachment is obsolete: true
Attachment #739045 -
Flags: review?(vyang)
Attachment #739097 -
Flags: review?(vyang)
Updated•12 years ago
|
Attachment #739097 -
Flags: review?(vyang) → review+
Assignee | ||
Comment 12•12 years ago
|
||
Assignee | ||
Comment 13•12 years ago
|
||
Attachment #739097 -
Attachment is obsolete: true
Attachment #739451 -
Attachment is obsolete: true
Attachment #739585 -
Flags: review+
Assignee | ||
Comment 15•12 years ago
|
||
Since the Madrid work week is finished, I'm not very sure we should land this patch to inbound or birch. Ask for checkin-needed. Try server looks fine.
Keywords: checkin-needed
Comment 16•12 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/cf284804c348
Keywords: checkin-needed
https://hg.mozilla.org/mozilla-central/rev/cf284804c348
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla23
Assignee | ||
Comment 18•12 years ago
|
||
https://hg.mozilla.org/releases/mozilla-b2g18/rev/dcdc2b74cff1 Per the conclusion during the work week in Madrid, we were in agreement we could land the MMS patches to the b2g18 branch. This patch doesn't touch the RIL interface change so it should be pretty safe to land.
status-b2g18-v1.0.0:
--- → wontfix
status-b2g18-v1.0.1:
--- → wontfix
status-firefox21:
--- → wontfix
status-firefox22:
--- → wontfix
status-firefox23:
--- → fixed
Whiteboard: [NO_UPLIFT]
Assignee | ||
Updated•12 years ago
|
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Updated•12 years ago
|
Updated•12 years ago
|
Attachment #741791 -
Flags: review?(vyang) → review+
Assignee | ||
Comment 20•12 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/0e8b99f4d0b3 https://hg.mozilla.org/releases/mozilla-b2g18/rev/6c2493de1441
Comment 21•12 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/0e8b99f4d0b3
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Flags: in-moztrap-
You need to log in
before you can comment on or make changes to this bug.
Description
•