Closed
Bug 840058
Opened 12 years ago
Closed 12 years ago
[MMS][User Story] Slide playback from message
Categories
(Firefox OS Graveyard :: Gaia::SMS, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: pdol, Unassigned)
References
Details
(Keywords: feature)
UCID: Messages-057
User Story:
As a user, I want to be able to initiate the playback of slides directly from a message (sent or received).
Updated•12 years ago
|
Depends on: b2g-mms-dom-api
Updated•12 years ago
|
Blocks: mms-userstories
Comment 1•12 years ago
|
||
Is this an special requirement from customer or FFOS feature ?
Due to this feature only exist in feature phone before, Please help to confirm this feature is needed.
Comment 2•12 years ago
|
||
Sorry, Please ignore my post 2013-02-18 01:01:13 PST .
Updated•12 years ago
|
Blocks: b2g-mms-ui
Comment 3•12 years ago
|
||
(In reply to Neo Hsieh from comment #1)
> Is this an special requirement from customer or FFOS feature ?
>
> Due to this feature only exist in feature phone before, Please help to
> confirm this feature is needed.
needinfo? product
Flags: needinfo?(ffos-product)
Comment 4•12 years ago
|
||
Is this really a P1? I found it on Android now because I was trying to understand this story, but I was never aware of it before. There's a good deal of work in here to create the interface for choosing, ordering, and playback of slides for a feature I would guess has very low usage.
Flags: needinfo?(pdolanjski)
Reporter | ||
Comment 5•12 years ago
|
||
(In reply to Dylan Oliver [:doliver] from comment #4)
> Is this really a P1? I found it on Android now because I was trying to
> understand this story, but I was never aware of it before. There's a good
> deal of work in here to create the interface for choosing, ordering, and
> playback of slides for a feature I would guess has very low usage.
I apologize. This was a mistake. It should be marked OOS in the User Story spreadsheet. I've now updated it.
For leo, we will consider bug 840085 only.
Status: NEW → RESOLVED
blocking-b2g: leo+ → ---
Closed: 12 years ago
Flags: needinfo?(pdolanjski)
Flags: needinfo?(ffos-product)
Resolution: --- → WONTFIX
Updated•12 years ago
|
Priority: P1 → --
Comment 6•12 years ago
|
||
Hi, bug 840063 ([User Story] OMA MMS v1.2 compliance) depends on bug 792319 (Gecko mandatory conformance items), which depends on bug 792326 (MMS Core Content Domain), which says we should support at least one content class, and some MMS client like Android does implement all. So for better compatibility, we'd better at least support displaying SMIL slides.
Comment 7•12 years ago
|
||
i believe we should fulfill the minimum requirement for MMS v1.2 compliance
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Updated•12 years ago
|
Flags: needinfo?(pdolanjski)
Reporter | ||
Comment 8•12 years ago
|
||
Do we know if implementing bug 840085 will satisfy compliance?
Flags: needinfo?(pdolanjski)
Updated•12 years ago
|
Flags: needinfo?(vyang)
Comment 9•12 years ago
|
||
(In reply to Peter Dolanjski [:pdol] from comment #8)
> Do we know if implementing bug 840085 will satisfy compliance?
If I understand correctly bug 840085 is about another thing. OMA-TS-MMS-CONF-V1_3-20110913-A section 10.3 "General Interoperability Requirements":
> If the MMS Client receives an MM that contains corrupted
> content or content that is not supported by the terminal, then
> the MMS Client SHALL employ best effort in presenting the MM.
But in section 4.1 "Usage of SMIL" of the same document has:
> The MMS messages compliant with this interoperability document
> will use the Synchronized multimedia Integration Language
> (SMIL) as the presentation language ([SMIL]).
So basically all conforming MMS messages should have a SMIL document in it. And in this bug, we're talking about slides, which follows there must already be a SMIL document in that MM. Then section 5.2 "Structure" has:
> The multimedia messages of the Core MM Content Domain (section
> 6) SHALL consist of a "slide show"
And as I replied in comment #6, supporting full core content domain is not listed as a mandatory conformance item, neither does slide-based SMIL presentation. But the latter seems to be a very basic convention in using SMIL, so I suggest we at least support displaying slide animations without creating them.
Flags: needinfo?(vyang)
Comment 10•12 years ago
|
||
per sync with Taipei team, slide show is an optional item in conformance. This item does not block release.
Updated•12 years ago
|
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → WONTFIX
Comment 11•12 years ago
|
||
Just to be clear, the intent of this user story was to ensure that if a message is received that uses SMIL, the user will be able to view it on the device. It was flagged as a P1 because it may be an interoperability issue if our device cannot display the content in an MMS (e.g. if there were two slides, each with an image, can the user see both images or would they not see anything or only one, etc.). The primary goal was to identify that the device may receive a SMIL-encoded MMS, and should be able to render the attachments to the user.
If this is wontfix, could we identify what the UX will be should a message using slides be recieved?
Comment 12•12 years ago
|
||
reopen before comment 11 is clearly understood
Steve, can you provide initial comment? thanks
Status: RESOLVED → REOPENED
Flags: needinfo?(schung)
Resolution: WONTFIX → ---
Comment 13•12 years ago
|
||
It's not about "slide show". It's about displaying MMS in SMIL.
Comment 14•12 years ago
|
||
SMIL defines the some information for the slide playback. If we only want to show the media and text in the view, there is no need to decode SMIL completely. We should have no problem in displaying all the media and text no matter the message is SMIL-encoded or not, the only question is should we have the ability to play slideshow directly in the message app?
Flags: needinfo?(schung)
Updated•12 years ago
|
Comment 15•12 years ago
|
||
Confirmed with team that all SMIL media is displayed by default, which sounds like it meets the criteria discussed here, so -> WFM.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•