UCID: WAPPush-003 User Story: As a user, I want to be able to receive WAP Push messages in my Messages Inbox so that I can receive messages an Operator or Operator service delivers to me.

Clearing tracking-b2g18 flag from User Story bugs. This flag is for bugs that we would take fixes for in the 1.x branch. Feature work should be officially slotted into a release instead with leo+. If this story is intended for v1.1, please nominate for leo? blocking.

Hi Peter, I got two question about this story. Does WAP Push messages retain in message inbox until it is deleted or expires, even after rebooting? Also, there are many types of WAP Push messages, and might be some provider-specific messages. Some of them are not supposed to be shown. What kinds of message do we have to support in this story?

Adding Kev to provide those answers.

(In reply to Peter Dolanjski [:pdol on PTO until April 16th]] from comment #0) > UCID: WAPPush-003 > > User Story: > As a user, I want to be able to receive WAP Push messages in my Messages > Inbox so that I can receive messages an Operator or Operator service > delivers to me. I don't know why you wan WAP Push messages in your message box. WAP Push messages could be binary encoded blobs and there are actually tons of different message formats. They don't match the semantics of a message app because they're usually used as notifications for further services, not messages you send and received from others.

Note that we don't need to modify the SMS/MMS API to support this. The comms app could listen for WAP messages and store those messages manually. It does mean merging a local indexedDB database with the results from getThreadList, but I think that should be fine as it's not very much data.

Per comment #4, WAP push should not go into the inbox. It's intended to display a modal dialog with an OK (go to linked content) or Cancel (close the modal dialog).

Based on comment #6, moving to WONTFIX.