948260 - [User Story] Navigate between videos in the video app

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::Video, defect, P2)

Description

[Sri Kasetti]

User Story:
As a user, when I am in the video app I like to navigate between videos using "Play Previous" and "PlayNext" so that I can move from one video to the next without having to get back to the gallery view

Comment 2

[Dominic Kuo [:dkuo]]

Needinfo Chris and Rob to catch ux team's attention.

Comment 3

[Rob MacDonald [:robmac]]

Hi everyone - This will be covered under a spec that Jacqueline will be posting to bug 951025. The proposal will be posted later today. - Rob

Needsinfo'ing Jacqueline as an fyi.

Comment 4

[John Hu [:johnhu][:johu][:醬糊小弟]]

Hi all,

About swipe to navigate, it may not easy to implement. Because we only have one video decoder in our devices. We may need to use a thumbnail image for another video or use two thumbnail images for both video files. The video player in video app is different than gallery app. We use video element to load the video file directly instead of loading thumbnail image first. While swiping, gallery app uses two images to do the transition. But in video app, we may need to pause the video element and load another image for swiping. There may be two issues here:

1. which image do we use and the image quality
    The only thumbnail image we current have is the image for list view. That image is created at a fixed resolution, 210x120. The algorithm of thumbnail image is to fit the video file into a 210x120 rectangle. When the video's ratio is not the same as 210x120, it fills black at the other place. So, a portrait video will be scaled down to fit into 120px in its hight, and the scale ratio will be high. If we use a portrait video in landscape layout, the quality of this image may be bad. In gallery app, it respects video resolution ratio to create thumbnail image and use css to place the thumbnail image into the list view. If we use the same algorithm here, it may give us an acceptable image quality in fullscreen view and may have a manageable scaling ratio.

2. loading performance
    If we use one image and one video for swiping, we may need to handle the time of video loaded and first frame decoded while swiping quickly. To compare the loading time of image and video, I may prefer to use two images for swipe transition. After the transition is finished, we use video element to load the video file but not auto-play. The timing of video loading may be an issue here.. If we use two images for transition, the timing to load the video file may be critical when user swipe quickly. In gallery app, we load the video when user tap the play button. We may use the same policy to do so.

Comment 5

[John Hu [:johnhu][:johu][:醬糊小弟]]

comments by Sireesha:
Navigating between Previous and Next Video(Bug 948260)implementation needs the below changes.

1.Like Gallery app,Video app needs to maintain an global array and this array is initially filled when we enumerate video database, and has elements added and removed when we receive create and delete events from the media databases.

2.Like Gallery app,Video app UI need to maintain 3 <div> elements for prev,current and next Videos be to displayed.But current video app UI is using single <video> element.

3.Video app need to include transition related css similar to Gallery app.

Along with the below points mentioned by John,prev/next video navigation of UI spec is little complex and need more code changes in Video app.

Comment 6

[Rob MacDonald [:robmac]]

Hi everyone...

To confirm, I agree with the approach outlined in Wayne's email today. Although we will retain the FF/REW as specified, we will drop the previous / next behaviour for now. Please NI me if I've misunderstood or if this changes.

Thanks!
Rob

Comment 7

[BMO Automation]

Firefox OS is not being worked on