Closed
Bug 840082
Opened 12 years ago
Closed 12 years ago
[MMS][User Story] Image, audio and video format support
Categories
(Firefox OS Graveyard :: Gaia::SMS, defect, P1)
Tracking
(blocking-b2g:-)
RESOLVED
FIXED
blocking-b2g | - |
People
(Reporter: pdol, Assigned: schien)
References
Details
(Keywords: feature, Whiteboard: [3/11~3/15])
Attachments
(1 obsolete file)
UCID: Messages-012
User Story:
As a user, I can send, receive, and view MMS messages with JPEG images, AMR-NB, H.263 & AMR so that I can view content that is commonly exchanged via MMS.
Updated•12 years ago
|
Depends on: 792326, b2g-mms-dom-api
Updated•12 years ago
|
Blocks: mms-userstories
Sounds more like a technical requirement.
UX is defined in bug #840044
Comment 3•12 years ago
|
||
Multimedia format compliance will be checked against OMA-TS-MMS-CONF-V1_3-20110913-A section 7, and Appendix C.1.2
Updated•12 years ago
|
Whiteboard: [3/11~3/15]
Comment 4•12 years ago
|
||
If AMR is required for B2G please ensure that it only works for internal B2G applications and not on the "web platform" via the browser.
Assignee | ||
Comment 5•12 years ago
|
||
Implementation is referenced from bug 182621. I can wrap these modification with compile option if we only want support WBMP on Firefox OS.
Attachment #721569 -
Flags: review?(joe)
Assignee | ||
Comment 6•12 years ago
|
||
Comment on attachment 721569 [details] [diff] [review]
implement WBMP decoder
sorry, wrong bug.
Attachment #721569 -
Attachment is obsolete: true
Attachment #721569 -
Flags: review?(joe)
Comment 7•12 years ago
|
||
As far as I know, Firefox OS does not support H.263 yet, right?
Comment 8•12 years ago
|
||
Per partner and release-driver discussions, marking blocking- until all MMS functionality in bug 849867 is complete, allowing it all to be uplifted at once to avoid SMS bustage.
blocking-b2g: leo+ → -
Comment 9•12 years ago
|
||
http://technical.openmobilealliance.org/Technical/release_program/docs/MMS/V1_2-20050429-A/OMA-MMS-CONF-V1_2-20050301-A.pdf
for minimum conformance on MM Content Classes, only need to support Text and Image Basic
For Video/Audio/Image, only these are mentioned:
Baseline JPEG,
GIF87a,
GIF89a,
WBMP,
AMR-NB or 13K
It's important that Gecko support for legacy non-Web formats be restricted as much as possible to the use-cases where they're absolutely needed. In particular we don't want Web developers or non-MMS app developers using them either on purpose or accidentally.
When performance isn't too much of a concern, one way would be to implement support for the format in JS in the app itself. This should work for most image formats using JS to decode to canvas. This also has the technical advantage that the image decoding is effectively sandboxed.
Once we have Web Audio implemented (not on the 18 branch) it would probably work for audio formats such as SP-MIDI, although it would be more work.
Updated•12 years ago
|
Flags: in-moztrap?
Comment 11•12 years ago
|
||
what's the latest on this bug? thanks
Assignee | ||
Comment 12•12 years ago
|
||
This bug is mostly like a meta bug which has splitted into 3 bugs for supporting WBMP/AMR-NB/SP-MIDI.
Patches for WBMP and AMR-NB were ready in b2g18, and per our previous discussion SP-MIDI will be excluded from the v1.1 scope. We can mark this bug as resolved IMO.
Comment 13•12 years ago
|
||
per comment 12, mark as resolved and waiting for verification
Status: NEW → RESOLVED
Closed: 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
•