Closed Bug 840037 Opened 12 years ago Closed 12 years ago

[MMS][User Story] MMS US-ASCII, UTF-8, UTF-16 message encoding

Categories

(Firefox OS Graveyard :: General, defect, P1)

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-b2g:-)

RESOLVED FIXED
blocking-b2g -

People

(Reporter: pdol, Assigned: vicamo)

References

Details

(Keywords: feature, Whiteboard: [LOE:0])

UCID: Messages-010 User Story: As a user, I can send and receive plain text MMS messages encoded in US-ASCII, UTF-8, UTF-16 to ensure that messages sent to or received from other devices can be read by their respective user(s).
Depends on: 792328
vicamo: can you take this? thanks
Assignee: nobody → vyang
Component: Gaia::SMS → General
QA Contact: mbarone976
Already landed. pending verification
Whiteboard: [LOE:S]
Whiteboard: [LOE:S] → [LOE:0]
Blocks: mms-p1
Per partner and release-driver discussions, marking blocking- until all MMS functionality in bug 849867 is complete, allowing it all to be checked-in at once to avoid SMS bustage.
blocking-b2g: leo+ → -
Flags: in-moztrap?
change this to resolved fixed and waiting for verification
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
The test cases are already in moztrap: MMS_tef suite, bug840037 label. Although need to be updated, will do that. And once updated should be moved to MMS suite to be available for future test runs. Paul, I will let you know so you can take them.
Flags: needinfo?(pyang)
Flags: in-moztrap?
Flags: in-moztrap+
Thanks for information, please tell me if you're ready.
Flags: needinfo?(pyang)
Hi Paul, Test cases for UTF-8 and ASCII are ready. #8282,#8283
You need to log in before you can comment on or make changes to this bug.