Closed Bug 1068633 Opened 5 years ago Closed 5 years ago

Firefox: User doesn't go back to the channel after watching video till the end

Categories

(Firefox for Android :: Screencasting, defect, P2)

x86_64
Windows 7
defect

Tracking

()

VERIFIED FIXED
Tracking Status
fennec 33+ ---

People

(Reporter: jchaulk, Assigned: mfinkle)

Details

Attachments

(1 file)

Roku Bug# 42288

Channel information: v1.0 build 0

App version: 33.0

Android version: 4.0.4

Platform/Firmware:
Giga – 5.5.410
Austin – 5.5.415
Jackson – 5.5.411
Tyler – 5.5.428
Sugarland – 5.5.2032
Paolo – 5.5.433
Liberty (Hisense) – 6.0.5029
Liberty (TCL) – 6.0.5029

Steps to reproduce:
1. Add the channel to Roku player.
2. Launch the channel.
4. Go to 'View recent history'
5. Launch playback.
6. Wait till playback finishes.

Expected Result: user navigates back to the channel

Actual Result: video freezes

Reproducibility: always
Assignee: nobody → mark.finkle
tracking-fennec: ? → 33+
This was easy.

We just need to return after the video stream completes. This works fine when playing videos from the "recent history" screen, as well as, from Firefox client.
Attachment #8493531 - Flags: review?(wjohnston)
Attachment #8493531 - Flags: review?(wjohnston) → review?(bnicholson)
Attachment #8493531 - Flags: review?(bnicholson) → review+
https://github.com/mozilla/firefox-roku/commit/0ef3fd5b72f93016b946b84070f33bbad38a29fd
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
'Recent History' page is displayed on Roku after viewing a video from the 'Recent History'.

Firefox channel is not resumed after successfully casting a video from Firefox for android. 
Is this the expected behavior?
(In reply to Flaviu Cos, QA [:flaviu] from comment #3)
> 'Recent History' page is displayed on Roku after viewing a video from the
> 'Recent History'.
> 
> Firefox channel is not resumed after successfully casting a video from
> Firefox for android. 
> Is this the expected behavior?

Correct
Verified as fixed in Firefox Nightly for Roku v1.2.
Device: Roku 2.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.