Closed Bug 868123 Opened 12 years ago Closed 12 years ago

[MMS] handle messages with bad SMIL/content-id

Categories

(Firefox OS Graveyard :: Gaia::SMS, defect)

x86
macOS
defect
Not set
normal

Tracking

(blocking-b2g:leo+, b2g18+ fixed)

RESOLVED FIXED
blocking-b2g leo+
Tracking Status
b2g18 + fixed

People

(Reporter: gnarf, Assigned: gnarf)

References

Details

Attachments

(1 file)

Some MMS apps (Handcent on Android) are sending video with incorrect content-id headers, and this causes completely empty parsing. I feel like if the SMIL content tries to reference an attachment that isn't found we should be rendering the MMS as if there hadn't been any SMIL (just string the attachments together in order)
Assignee: nobody → gnarf37
Attachment #744772 - Flags: review?(felash)
blocking-b2g: --- → leo?
(In reply to Corey Frang [:gnarf] from comment #0) > Some MMS apps (Handcent on Android) are sending video with incorrect > content-id headers, and this causes completely empty parsing. I feel like > if the SMIL content tries to reference an attachment that isn't found we > should be rendering the MMS as if there hadn't been any SMIL (just string > the attachments together in order) Is supporting malformed MMS cases a rabbit hole? If so, we may take an approval here but not commit to blocking on incorrect behavior. Also, how prevalent is this malformed MMS?
I doubt we will see many of these, but adding a little protective logic to take something where there would be a completely empty message bubble and instead it displays whatever it can.
This is easy enough to handle this in a protective way so let's do it. Leo+, or approval, I don't mind. I agree this is less important than the other mms stuff though.
r=me
reviewed on the PR. A small change + a question to be answered.
master: 114bf216de0a19f7a6e2f63234b4a7a37fff9408
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment on attachment 744772 [details] [review] https://github.com/mozilla-b2g/gaia/pull/9516 NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings. [Approval Request Comment] Bug caused by (feature/regressing bug #): - User impact if declined: some badly produced MMS won't show correctly Testing completed: yes Risk to taking this patch (and alternatives if risky): low, this code unit is unit tested String or UUID changes made by this patch: none This is likely not a blocker but a low-risk nice to have.
Attachment #744772 - Flags: approval-gaia-v1?(21)
Triage: tracking+, will leave it to Vivien for approval.
blocking-b2g: leo? → -
tracking-b2g18: --- → +
Attachment #744772 - Flags: approval-gaia-v1?(21) → approval-gaia-v1+
Uplifted 114bf216de0a19f7a6e2f63234b4a7a37fff9408 to: v1-train: b855df38369ad82eae5053796a6a7910d5beb959
Blocks: 875619
blocking-b2g: - → leo?
blocking-b2g: leo? → leo+
Attachment mime type: text/plain → text/x-github-pull-request
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: