Video doesn't pause properly on mobile

RESOLVED WORKSFORME

Status

()

Firefox for Android
Audio/Video
RESOLVED WORKSFORME
2 years ago
a year ago

People

(Reporter: mkaply, Assigned: fatseng)

Tracking

({compat})

Trunk
compat
Points:
---

Firefox Tracking Flags

(firefox50 affected)

Details

(URL)

(Reporter)

Description

2 years ago
Going to this URL on Fennec:

http://www.iqiyi.com/v_19rrlmg4c4.html

When clicking on the video, the pause button appears, but the pause doesn't work.

Other interaction with the video doesn't work either (seeking, full screen).

Also, the video continues to play after pushing the home button.
(Reporter)

Comment 1

2 years ago
This happens on desktop as well if you completely remove Flash and use a mobile user agent.

It seems like there an image over the video, but the partner indicates that it works fine on Chrome mobile (and I verified that).
Sounds like webcompat. Mike would you have a look?
Flags: needinfo?(miket)
I have tried it on chrome on Android. It can work well. 
With our nightly, pause cannot work with website UI but if we use the UI on our newly-added notification, it can work.
Keywords: compat
Component: General → Audio/Video
Farmer,
Debugging this bug should help you understand how media element handles play and pause. 
Have fun! :-)
Flags: needinfo?(fatseng)
(Assignee)

Comment 5

a year ago
I am interested in this and will have a look later.
Flags: needinfo?(fatseng)
Looks like Farmer is gonna look into this, clearing ni? But feel free to re-ping me if I can help with anything.

(apologies for delay, just coming off PTO).
Flags: needinfo?(miket)
(Assignee)

Comment 7

a year ago
I tried fennect-50.0a1, the pause button works fine.
But I found one symptom is interesting.
If I press play button then press pause button immediately, the video is stopped a while then be played. google-chrome also could see this symptom.
It is front end problem. Since this front end calls HTMLMediaElement::Play twice by postMessage, if you press play and pause quickly, the latest HTMLMediaElement::Play is called behind HTMLMediaElement::Pause.
Therefore, the video is stopped a while then be played. 
Is this symptom you facing?
Flags: needinfo?(mozilla)
(Reporter)

Comment 8

a year ago
There were two symptoms, one that you can't pause at all and one that navigating away from Firefox via the home button doesn't pause the video. 

If either of these works in 50,I'd like to find what fixed it and back port.
Flags: needinfo?(mozilla)
(Assignee)

Updated

a year ago
Assignee: nobody → fatseng
(Assignee)

Comment 9

a year ago
To Playback video in background is Fennec's feature.
Please help try pause function in 50.
Flags: needinfo?(mozilla)
(Assignee)

Comment 10

a year ago
(In reply to Farmer Tseng[:fatseng] from comment #7)
> I tried fennect-50.0a1, the pause button works fine.
> But I found one symptom is interesting.
> If I press play button then press pause button immediately, the video is
> stopped a while then be played. google-chrome also could see this symptom.
> It is front end problem. Since this front end calls HTMLMediaElement::Play
> twice by postMessage, if you press play and pause quickly, the latest
> HTMLMediaElement::Play is called behind HTMLMediaElement::Pause.
> Therefore, the video is stopped a while then be played. 
> Is this symptom you facing?

When pressing play, front end calls twice play.
There is 1 second gap between first play and second play.
This is website front end's problem.
07-06 18:24:48.628 I/Gecko   (27822): HTMLMediaElement::Pause
07-06 18:24:48.630 I/Gecko   (27822): HTMLMediaElement::Play
07-06 18:24:49.634 I/Gecko   (27822): HTMLMediaElement::Play
(Reporter)

Comment 11

a year ago
This does appear to be working on Firefox 48 now. Not sure what changed.
Status: NEW → RESOLVED
Last Resolved: a year ago
Flags: needinfo?(mozilla)
Resolution: --- → WORKSFORME
(Reporter)

Comment 12

a year ago
I'm thinking they changed something on the website because it works in 47 now as well (and looks a little different)
You need to log in before you can comment on or make changes to this bug.