Closed Bug 1036369 Opened 10 years ago Closed 10 years ago

Seek pointer doesn't return to the beginning of the playback when the forward key is pressed during the end of the playback

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(b2g-v2.0 affected, b2g-v2.1 affected)

RESOLVED INVALID
Tracking Status
b2g-v2.0 --- affected
b2g-v2.1 --- affected

People

(Reporter: poojas, Assigned: rnicoletti)

References

Details

(Whiteboard: [caf priority: p2][CR 691060])

When the playback is about to complete, and if we tap on the forward button, seek pointer stays at the end of the seek bar and doesn’t return to the beginning. This is observed with all type of clips

Steps to reproduce:

1) Load any video clip on the device
2) When the playback is about to complete, tap on forward button.

Actual behavior: Seek pointer will stay at the end and will not return to the beginning.

Expected behavior: Seek pointer stays at the end of the playback
**Typo in above mentioned bug detail:**
Expected behavior: Seek pointer should return to the begning of the playback.
blocking-b2g: --- → 2.0?
Whiteboard: [CR 691060] → [caf priority: p2][CR 691060]
QA Wanted for branch checks.
Keywords: qawanted
Issue is reproducible on Flame 2.0, Flame 2.1 master, and Buri 2.1 master.

Tapping on Forward button toward the end of the video makes the seek button to stay at the end. This issue only occurs in Video app because the Backward and Forward buttons are only implemented in Video app.

Device: Flame
Build ID: 20140709085028
Gaia: 3316542e36084a8d1f6a5446abe9bf199765f3d7
Gecko: 394b7c158cf0
Version: 32.0a2 (2.0)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Device: Flame
Build ID: 20140709070635
Gaia: c394b7b4205b6f1a6ca44915fc08650f3ad127ec
Gecko: 2d88803a0b9c
Version: 33.0a1 (Master)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0

Device: Buri
Build ID: 20140709070635
Gaia: c394b7b4205b6f1a6ca44915fc08650f3ad127ec
Gecko: 2d88803a0b9c
Version: 33.0a1 (Master)
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0

--------

This issue doesn't occur in Flame 1.4 because Backward and Forward buttons are not implemented in Video app.

Device: Flame
Build ID: 20140709075131
Gaia: b0e9b4bdb39c5eb93a6783a34624ffc84f62b126
Gecko: ccabaf8826a4
Version: 30.0 (1.4)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Keywords: qawanted
blocking-b2g: 2.0? → 2.0+
This is not a regression. comment 3 implies this is a broken new feature bug.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
I wouldn't block a release on it, but certainly a convenience for user to return to beginning on hitting the forward button at the end of video playback. 

https://wiki.mozilla.org/B2G/Triage#Issues_that_Should_Block


Russ,

Can you check to see if you can address this and land on master. Based on the fix/risk, we can decide if we want to uplift to 2.0 or not.

Probably a missed aspect from this feature: https://bugzilla.mozilla.org/show_bug.cgi?id=951025

Thanks
Hema
Assignee: nobody → rnicoletti
Flags: needinfo?(rnicoletti)
This behavior was explicitly requested by UX. See https://bugzilla.mozilla.org/show_bug.cgi?id=951025#c13.

FWIW, it makes sense to me that the behavior of the forward button would be the same as the slider. For example, when moving the slider to the end of the video, the video is paused at the end, it doesn't go back to the beginning.

NI for pooja and mike to resolve the conflicting opinions.
Flags: needinfo?(rnicoletti)
Flags: needinfo?(poojas)
Flags: needinfo?(mtsai)
unblocking 2.0 release
blocking-b2g: 2.0+ → ---
(In reply to Russ Nicoletti [:russn] from comment #6)

> NI for pooja and mike to resolve the conflicting opinions.

HI Russ and MIke,

I belive typical behavior for forward button is to go back to the begning after playback ends.

but from
> This behavior was explicitly requested by UX. See
> https://bugzilla.mozilla.org/show_bug.cgi?id=951025#c13.
> 
looks like this is as per Mozilla's UX design. If so please double confirm
Flags: needinfo?(poojas) → needinfo?(rnicoletti)
Ni? video UX owner Tiffanie and Rob to follow up. Thanks.
Flags: needinfo?(tshakespeare)
Flags: needinfo?(rmacdonald)
Flags: needinfo?(mtsai)
This does appear to be as designed. NI'ing Jacqueline to confirm but, based on the spec in bug 951025 it seems pretty clear to me.
Flags: needinfo?(tshakespeare)
Flags: needinfo?(rmacdonald)
Flags: needinfo?(jsavory)
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
Also in bug 951025 its mentioned that Video app should behave as Music app.

In music app i have noticed that if you seek using slider till playback end then seek pointer goes back to the start instead if staying at end. Unlike Video app behavior
Same with forward button.

So can we know which behavior is as per spec i.e Music app's or Video app's?
When I try the music app I'm seeing that using the slider to move to the end of a song results in the music player moving to the next song. Also the forward button causes the player to move to the next song. 

Waiting to hear from Jacqueline.
Flags: needinfo?(rnicoletti)
As Rob mentioned, the video player seeker bar is working as designed. If the user wants to play the video after it has finished, they can tap the play button and the seeker bar will then begin at the beginning again.

Currently, it is different from Music as the buttons have different actions. The video fast forward button was never intended to go to the next video, unlike the music next button. Also, I am seeing a few issues about the ending of the seeker bar with music and will file a separate bug to cover those issues.
Flags: needinfo?(jsavory)
Based on comment #13, I'm resolving this bug as "invalid"
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.