Closed
Bug 1174441
Opened 9 years ago
Closed 9 years ago
[spark] Group texting doesn't work
Categories
(Firefox OS Graveyard :: Gaia::SMS, defect)
Firefox OS Graveyard
Gaia::SMS
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1106663
People
(Reporter: callahad, Unassigned, NeedInfo)
Details
(Keywords: feature, foxfood, Whiteboard: [bzlite][triagr])
User-Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0 I can't initiate or participate in group SMS threads. Also: When receiving a group text, it's grouped with the normal, individual texts from that contact in a way that's indistinguishable from an SMS, and it seems to be impossible to look up who the group message was sent to. For foxfooding, this significantly impairs my ability to communicate and coordinate with my friends in day to day life.
Updated•9 years ago
|
Component: Gaia::Feedback → Gaia::SMS
Flags: needinfo?(fxos.triage.feature)
Flags: needinfo?(fxos.triage.duplicate)
Whiteboard: [bzlite] → [bzlite][triagr]
Comment 1•9 years ago
|
||
Actually, there is no such things as group SMS threads. This is only group MMS. We do have a rather incomplete support for group MMS. Let me explain in several sentences the current status. 1. Sending You can send group MMS messages quite easily: you need to force the "MMS" status of a message. For example you can add a subject. This will also create a thread for a group conversation. Inside this group conversation you still have to force the "MMS" status to send group messages. 2. Receiving Due to a technical issue we haven't overcome yet, group MMS messages we receive are not shown as such. There's added in the thread for the sender. And there is no way to "reply to all". 3. Conclusion All I can say is that it's quite broken. I have a meta about this for some time now but we couldn't find the time to properly think about this yet. Mostly because nobody seemed interested to prioritize this work. I can only hope that one more report like yours can help prioritize. I'm especially arguing to at least make it possible for the user to enable at least an incomplete version of "receiving" but right now enabling the pref makes things worse. Duplicating to the meta bug 1106663.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 2•9 years ago
|
||
(In reply to Julien Wajsberg [:julienw] from comment #1) > And there is no way to "reply to all". It's worse than that -- there's not even a way to know who a group message was sent to, when receiving one. That information isn't visible in the long-press -> Message Report view. This means I can't communicate at all as a participant of a group MMS thread that I did not initiate.
Comment 3•9 years ago
|
||
Yeah you're right. We do have the code to show the multiple recipients in that element. I wonder if it would be costly for Gecko to at least keep this information. Could be a low-hanging fruit. Hey Bevis, what do you think? Could we at least keep the recipient information when receiving a group MMS (without changing the behavior for now)?
Flags: needinfo?(btseng)
Comment 4•9 years ago
|
||
(In reply to Julien Wajsberg [:julienw] from comment #3) > Yeah you're right. We do have the code to show the multiple recipients in > that element. I wonder if it would be costly for Gecko to at least keep this > information. Could be a low-hanging fruit. > > Hey Bevis, what do you think? Could we at least keep the recipient > information when receiving a group MMS (without changing the behavior for > now)? Hi Julien, The participants filtered out by MobileMessageDB is the one in thread record. However, this information is still available/stored in |MmsMessage.receivers|: https://dxr.mozilla.org/mozilla-central/source/dom/mobilemessage/interfaces/nsIDOMMozMmsMessage.idl#40 Gaia shall be able to retrieve this information from selected Mms message. :)
Flags: needinfo?(btseng)
Comment 5•9 years ago
|
||
OK, I was very convinced Gecko was filtering this out :) Needinfo me, I'll dig further and file a separate bug if necessary.
Comment 6•9 years ago
|
||
(In reply to Julien Wajsberg [:julienw] from comment #5) > OK, I was very convinced Gecko was filtering this out :) > > Needinfo me, I'll dig further and file a separate bug if necessary. FYI: I have tested this earlier and print out the log at [1][2] to double confirm this. :) [1] https://dxr.mozilla.org/mozilla-central/source/dom/mobilemessage/gonk/MmsService.js#1708 -> debug("BVS, aDomMessage.receivers: " + JSON.stringify(aDomMessage.receivers)); [2] https://github.com/mozilla-b2g/gaia/blob/9dfedd7d35da00fa9b08dcffc3ab4f47da54e4f0/apps/sms/services/js/message_manager.js#L72 -> console.log("BVS, message.receivers: " + JSON.stringify(message.receivers)); -- Receivers are available in message.receivers according to the log: 07-13 11:20:03.488 4858 4858 I Gecko : -@- MmsService: BVS, aDomMessage.receivers: ["+886926932591","+886953045255"] 07-13 11:20:03.778 5504 5504 I Messages: Content JS LOG: BVS, message.receivers: ["+886926932591","+886953045255"]
Comment 7•9 years ago
|
||
yes, actually, we can see in [1] that for received messages we display only the sender. This should be easy to change. I filed bug 1183074. [1] https://github.com/mozilla-b2g/gaia/blob/0585f7ec07d0ed12f5bb53e051d01d33b91288cb/apps/sms/views/conversation/js/information.js#L186-L188
You need to log in
before you can comment on or make changes to this bug.
Description
•