B2G MMS: MMSCONF-MED-C-0{06, 07, 08, 09, 10, 12, 15, 34, 35}: Support multiple media types

RESOLVED FIXED in Firefox 20

Status

()

Core
DOM: Device Interfaces
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: vicamo, Assigned: ctai)

Tracking

(Blocks: 2 bugs)

unspecified
mozilla20
ARM
Gonk (Firefox OS)
Points:
---
Dependency tree / graph
Bug Flags:
in-moztrap -

Firefox Tracking Flags

(blocking-b2g:leo+, firefox20 fixed, b2g18 fixed, b2g18-v1.0.0 wontfix, b2g18-v1.0.1 wontfix)

Details

Attachments

(2 attachments, 2 obsolete attachments)

(Reporter)

Description

5 years ago
See OMA-TS-MMS-CONF-V1_3-20110913-A section 7, 7.1.1, and Appendix C.1.12
See OMA-ETS-MMS_CON-V1_3-20101015-C section 5.1.2.2.1, 5.1.2.2.2, 5.1.2.2.3, 5.1.2.2.4, 5.1.2.2.5, 5.1.2.2.6, 5.2.3.2.1, 5.2.3.2.2, 5.2.3.2.3, 5.2.3.2.4, 5.2.3.2.5, 5.2.3.2.6, 5.2.3.2.9
(Reporter)

Updated

5 years ago
Blocks: 792326
(Reporter)

Comment 1

5 years ago
They are:
1) text/plain, encoding=us-ascii, utf-8, utf-16
2) image/jpeg
3) image/gif
4) image/vnd.wap.wbmp
5) audio/amr
6) vCard & vCalendar

But maybe we should just add as much media types as possible. Additional types to be addressed:
7) H.263 & AMR (3GP)
8) MP4
9) JFIF

Actually, I think we should just add everything listed in http://www.wapforum.org/wina/wsp-content-type.htm
(Reporter)

Updated

5 years ago
Blocks: 804679
(Reporter)

Updated

5 years ago
Depends on: 792328
Assignee: nobody → ctai
I think we should follow the OMNA WSP Content Type Numbers which listed in http://www.openmobilealliance.org/tech/omna/omna-wsp-content-type.aspx

Because the types listed in http://www.wapforum.org/wina/wsp-content-type.htm’ are from 0x00 to 0x4B. The Content Type Numbers which listed in http://www.openmobilealliance.org/tech/omna/omna-wsp-content-type.aspx are from 0x00 to 0x5A (0x51 - 0x5A is tbd). It looks like the wsp content type listed in OMA is latest one.
(Reporter)

Comment 3

5 years ago
(In reply to Chia-hung Tai [:ctai :ctai_mozilla :cht] from comment #2)
> I think we should follow the OMNA WSP Content Type Numbers which listed in
> http://www.openmobilealliance.org/tech/omna/omna-wsp-content-type.aspx

Thanks. Please also updates the url in the comments of WspPduHelper.jsm
(Reporter)

Updated

5 years ago
Depends on: 810203
Created attachment 683839 [details] [diff] [review]
Add all WSP content types into WSP_WELL_KNOWN_CONTENT_TYPES
Attachment #683839 - Flags: feedback?(vyang)
Created attachment 683846 [details] [diff] [review]
Add all WSP content types into WSP_WELL_KNOWN_CONTENT_TYPES
Attachment #683839 - Attachment is obsolete: true
Attachment #683839 - Flags: feedback?(vyang)
Created attachment 683849 [details] [diff] [review]
Add all WSP content types into WSP_WELL_KNOWN_CONTENT_TYPES
Attachment #683846 - Attachment is obsolete: true
Status: NEW → ASSIGNED
Comment on attachment 683849 [details] [diff] [review]
Add all WSP content types into WSP_WELL_KNOWN_CONTENT_TYPES

Please help to review this patch.
Thanks
Attachment #683849 - Flags: review?(vyang)
Try server log:
https://tbpl.mozilla.org/?tree=Try&rev=db17a8d8467e
(Reporter)

Comment 9

5 years ago
Comment on attachment 683849 [details] [diff] [review]
Add all WSP content types into WSP_WELL_KNOWN_CONTENT_TYPES

Review of attachment 683849 [details] [diff] [review]:
-----------------------------------------------------------------

Great!
Attachment #683849 - Flags: review?(vyang) → review+
Keywords: checkin-needed
(Reporter)

Comment 10

5 years ago
https://hg.mozilla.org/integration/mozilla-inbound/rev/255d09298f9b
(Reporter)

Updated

5 years ago
Keywords: checkin-needed
https://hg.mozilla.org/mozilla-central/rev/255d09298f9b
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla20
(Reporter)

Updated

5 years ago
No longer blocks: 804679
Blocks: 810203
No longer depends on: 810203
blocking-b2g: --- → leo?
For mms merge to b2g18.
blocking-b2g: leo? → leo+
Created attachment 722015 [details] [diff] [review]
[b2g18]001-bug-792330-fix
https://hg.mozilla.org/releases/mozilla-b2g18/rev/95eb3483678c
status-b2g18: --- → fixed
status-b2g18-v1.0.0: --- → wontfix
status-b2g18-v1.0.1: --- → wontfix
status-firefox20: --- → fixed
The entire set of clian's pushes was backed out for multiple reasons.
https://tbpl.mozilla.org/?tree=Mozilla-B2g18&rev=a0b06192f882

1.) The tree rules are clear that you are not to land on top of bustage. At the time you pushed, both B2G Mn and B2G xpcshell had bustage from prior commits that hadn't been backed out yet.
2.) The tree rules are also clear that you are to watch your pushes for any bustage and handle them accordingly. mozilla-inbound is the ONLY tree where this rule does not apply.
3.) Even after the earlier bustage was backed out, something in one of your many pushes was causing further B2G Mn failures as shown in the log below.
https://tbpl.mozilla.org/php/getParsedLog.php?id=20424173&tree=Mozilla-B2g18
4.) This isn't cause for backout by itself, but it is also strongly preferred to not push each commit individually as our build and testing resources are limited and doing so stretches them even thinner. Please limit your number of pushes as much as possible unless you have good reason for keeping them separate.
status-b2g18: fixed → affected
(Reporter)

Comment 16

5 years ago
https://hg.mozilla.org/releases/mozilla-b2g18/rev/99680a32f297
status-b2g18: affected → fixed
(Reporter)

Updated

5 years ago
Blocks: 840063

Updated

5 years ago
Flags: in-moztrap-
You need to log in before you can comment on or make changes to this bug.