Closed Bug 1082330 Opened 10 years ago Closed 10 years ago

[Graphics] Media player control panel is not shown in full screen mode

Categories

(Core :: Graphics, defect)

ARM
Gonk (Firefox OS)
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 1076783
Tracking Status
b2g-v2.1 --- unaffected
b2g-v2.2 --- affected

People

(Reporter: ethan, Unassigned)

Details

(Keywords: regression)

Steps to reproduce:
1. Open the browser app.
2. Navigate to a link of HTTP streaming or RTSP streaming.
   For example: http://10.247.24.86/t-mobile.mp4
3. Enter full screen mode.
4. Tap the screen.

Expected result:
We can see the player control, such as the slide bar, the play/pause button,
etc., by tapping the screen.

Actual result:
The player control it not shown anymore in full screen mode.
Hi Vivien,

I think it's a regression bug and harmful to usability.
Could you help to take a look of this issue?
Flags: needinfo?(21)
(In reply to Ethan Tseng [:ethan] from comment #0)
> Actual result:
> The player control it not shown anymore in full screen mode.
Typo.
The player control "is" not shown.
Hi Luke,

I think this bug is critical to usability.
Could you provide any feedback or suggestion?
Severity: normal → critical
Flags: needinfo?(lchang)
This control panel is rendered by Gecko. Vincent looked into a similar issue recently.


Hi Vincent,

Could you please help on this? Thanks a lot.
Flags: needinfo?(lchang) → needinfo?(vliu)
Summary: [Browser] Media player control is not shown in full screen mode → [Browser] Media player control panel is not shown in full screen mode
Quickly observing the frame behavior, and it seems that this issue is not the same I saw in bug 1044356. When I played a youtube and put it into full screen, tapping the screen didn't have any insert/remove BoxFrame. It seems there was no BoxFrame in frame tree during youtube playing. For this, I will then dump frame tree to know the detail.
Flags: needinfo?(vliu)
After tracking more detail, I found this is a regression. 

1. flame-kk with 2.0 gecko branch doesn't have this issue.
2. Tried to back to the bellow comment in master branch and doesn't have this issue.
   Gecko commit id: f10bc818e50753b991124dab0057ada418436fd8

I tried to do some reverts in videocontrols.xml, and it seems not working for the modifications. Maybe someone could give me any hint to figure out more quickly. Thanks
(In reply to Vincent Liu[:vliu] from comment #6)
> After tracking more detail, I found this is a regression. 
> 
> 1. flame-kk with 2.0 gecko branch doesn't have this issue.
> 2. Tried to back to the bellow comment in master branch and doesn't have
> this issue.
>    Gecko commit id: f10bc818e50753b991124dab0057ada418436fd8
> 
> I tried to do some reverts in videocontrols.xml, and it seems not working
> for the modifications. Maybe someone could give me any hint to figure out
> more quickly. Thanks

Request the regression-window check since current master is already broken.
Hi Vincent and Peter,

I tried the latest gecko on mozilla-central today.
The control panel is gone even if the player is not in full screen mode.
It is not shown in either browser or youtube app.

Should we file another bug to track it?
Flags: needinfo?(vliu)
Flags: needinfo?(pchang)
It is obviously we have another regression according to Comment 8. From the description in Comment 8, it could be another use case. I think filing a new bug to track them separately is a good idea.
Flags: needinfo?(vliu)
Component: Gaia::Browser → Graphics
Product: Firefox OS → Core
Version: unspecified → Trunk
As discussed with Liu offline, adjust the component to a proper one.
Summary: [Browser] Media player control panel is not shown in full screen mode → [Graphics] Media player control panel is not shown in full screen mode
(In reply to Vincent Liu[:vliu] from comment #9)
> It is obviously we have another regression according to Comment 8. From the
> description in Comment 8, it could be another use case. I think filing a new
> bug to track them separately is a good idea.

Bug 1085787 was filed. :)
Nominate as blocking 2.2 now, change according after regression window is found.
blocking-b2g: --- → 2.2?
Keywords: regression
clear the ni since bug 1085787 is tracking this issue now.
Flags: needinfo?(pchang)
Clear the NI from Vivien since others are already tracking this issue.
Flags: needinfo?(21)
I should still able to find the regression window in master PRIOR to bug 1085787 occurring.

Quick branch check results:

Issue is reproducible in the following 2.2 master build:

Device: Flame (shallow flash)
BuildID: 20141018032012
Gaia: 1daf2dadcd0d554c733661a4c0be1b82001e9da0
Gecko: 33c0181c4a25
Version: 36.0a1 (2.2 Master)
Firmware: V188
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0

-------

Issue is NOT reproducible on Flame 2.1.

Device: Flame (shallow flash)
BuildID: 20141021142533
Gaia: 3d9cc667f4e929861a9a77c41096bbf5a9c1bde0
Gecko: 928b18f7d8ff
Version: 34.0 (2.1)
Firmware: V188
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

-------

Looking for a window now.
QA Contact: pcheng
I believe this bug is being dealt with in bug 1076783.

Removing window-wanted tag.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmercado)
Adding qawanted to check that the fixes for bug 1076783 also fixed this issue (making this a dupe) after bug 1085787 no longer blocks reproduction attempts.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmercado)
Keywords: qawanted
This bug is verified fixed on my Flame with the latest v2.2.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Removing qawanted tag due to bug being marked as resolved.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Keywords: qawanted
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
blocking-b2g: 2.2? → ---
You need to log in before you can comment on or make changes to this bug.