1011795 - [gallery][camera][video] share playback control between gallery, video, and camera

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia, defect)

Description

[Tiffanie Shakespeare [:tif]]

Currently it appears that Camera and Gallery share the same playback controls for videos, but the Video app does it's own thing.

In Mozilla Master, it's not obvious because the controls look and behave the same way. But there is a patch in the works for Video to add in some more playback controls - see Bug 951025 - so these will behave differently.

It would be rad if the three apps could share the same playback controls so the behaviour is consistent for all video playback.

It would also be awesome if we could take the patch mentioned above and make these improvements to it:
Bug 1011779 - [video] playback should pause for action menus and dialogues
Bug 1011791 - [video] playback progress is not smooth

Comment 3

[No-Jun Park [:njpark]]

Hema, can we mark this bug with higher priority for 3.0?  Some of the functional test failures also point to this bug as well.

Comment 4

[Hema Koka [:hema]]

Russ is working on playback controls web component and once that is ready we can share that for camera/video/gallery use.

Thanks
Hema

Comment 5

[Tiffanie Shakespeare [:tif]]

Is there anything needed from the UX side of things?

Comment 6

[Russ Nicoletti [:russn]]

The playback controls web component is unfortunately quite stale at this point. When I left off, I was trying to integrate the gaia-slider web component. IIRC, that was problematic. There are two versions of the component on github, one without gaia-slider [1], one with [2]. I believe the big problem with [2] is dragging the slider while the video is playing.

[1] http://russnicoletti.github.io/media-controls/
[2] http://russnicoletti.github.io/media-controls-gaia-slider/

If you'd like to play with them and provide feedback, that would be appreciated.

Comment 7

[Justin D'Arcangelo [:justindarc]]

I have recently built similar controls using web components for the Music app. We could probably look at pulling them out as more general Gaia components to use across all these apps. We've got two components: the time scrubber (which uses l20n.js for localizing time formatting) and the "play/pause, previous, next" controls (as a single component).

Comment 8

[Justin D'Arcangelo [:justindarc]]

I should also add that the time scrubber component in the Music app *should* work well for videos as well since <video> and <audio> share most APIs.

Comment 9

[Tiffanie Shakespeare [:tif]]

Great! Adding NI to take a look during UX triage. Thanks

Comment 10

[Rob MacDonald [:robmac]]

I think this warrants working on a small interaction spec that includes music, video and the built in browser player. The spec would include progress counters, handle behaviour, low and high speed scrubbing and more. This also requires a visual pass.

NI'ing Jacqueline and Hung to look at this in January. Happy new year! :)

Comment 11

[Hung Nguyen]

Clearing NI until interaction has been looked at. Jacqueline, let me know if you need anything.

Comment 12

[BMO Automation]

Firefox OS is not being worked on