Closed
Bug 802293
Opened 12 years ago
Closed 12 years ago
B2G MMS: MMSCONF-CAD-C-002: Support of UAProf for MMS Client capability negotiation
Categories
(Core :: DOM: Device Interfaces, defect)
Tracking
()
People
(Reporter: vicamo, Assigned: vicamo)
References
Details
See OMA-TS-MMS-CONF-V1_3-20110913-A section 9.5.1, and Appendix C.1.13
Comment 1•12 years ago
|
||
It seems the document should OMA-TS-MMS_CONF-V1_3-20110511-C section 9.5.1, and Appendix C.1.13
Status: NEW → ASSIGNED
Updated•12 years ago
|
Status: ASSIGNED → NEW
Comment 2•12 years ago
|
||
Add some comments from vyang's email about UAProf.....
Please see below comments from vyang.
UAProf (User Agent Profile) is an OMA specification[1] concerning device
capabilities and preferences. In summary, a supporting device sends the
URL or full binary encoded profile to a remote server during some
protocol initiation process. Since different devices have different
harware/software profiles and preferences, there won't be a such profile
file in Firefox OS code base, but a configurable preference for the
device-maker hosted URL.
In MMS, the only place may relate to UAProf in Firefox OS, we've already
supported sending UAProf URL if Gecko pref "wap.UAProf.url" is set [2].
However, because MMS is not for v1.0, the patch was only landed in m-c
trunk and is not available in b2g18. Even we re-land it in b2g18, there
is no where that will trigger such profile url reporting. In Android,
UAProf URL is only used in the same scenario -- MMS. So, in my opinion,
we'll need more detailed items about what to do to support UAProfile on
a device that has no MMS.
[1]:
http://www.openmobilealliance.org/Technical/release_program/uap_v11.aspx
[2]: https://bugzilla.mozilla.org/show_bug.cgi?id=804754
(In reply to Chia-hung Tai [:ctai :ctai_mozilla :cht] from comment #2)
> Even we re-land it in b2g18, there
> is no where that will trigger such profile url reporting. In Android,
> UAProf URL is only used in the same scenario -- MMS.
The plan is still to keep the UAProf URL for MMS only and not to send it when browsing or loading resources from installed Web apps over HTTP, right?
Assignee | ||
Comment 4•12 years ago
|
||
(In reply to Henri Sivonen (:hsivonen) from comment #3)
> The plan is still to keep the UAProf URL for MMS only and not
> to send it when browsing or loading resources from installed
> Web apps over HTTP, right?
UAProf is MMS only. Normal internet browsing doesn't need it at all.
Comment 6•12 years ago
|
||
leo+, this bug is needed to fulfill MMS user stories for v1.1
blocking-b2g: --- → leo+
Comment 7•12 years ago
|
||
this is supported already.
refer to bug 804754
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
status-b2g18:
--- → fixed
Assignee | ||
Updated•12 years ago
|
Blocks: mms-oma-compliance
Updated•12 years ago
|
Flags: in-moztrap-
You need to log in
before you can comment on or make changes to this bug.
Description
•