Open Bug 1282075 Opened 8 years ago Updated 2 years ago

Selecting the "Hide Controls" option causes the container area to disappear (for audio files played inline)


(Toolkit :: Video/Audio Controls, defect, P3)




Tracking Status
firefox48 --- affected
firefox49 --- affected
firefox50 --- affected
firefox-esr60 --- affected
firefox-esr102 --- affected
firefox64 --- affected
firefox65 --- affected
firefox66 --- affected
firefox67 --- affected
firefox68 --- affected
firefox69 --- affected
firefox70 --- affected
firefox71 --- affected
firefox72 --- affected
firefox73 --- affected
firefox74 --- affected
firefox75 --- affected
firefox76 --- affected
firefox77 --- affected
firefox78 --- affected
firefox79 --- affected
firefox80 --- affected
firefox81 --- affected
firefox82 --- affected


(Reporter: cbadau, Unassigned)



- This is a follow-up issue of bug 1222669.

[Affected versions]:
- Firefox 48 Beta 3
- latest Nightly 50.0a1
- latest Aurora 49.0a2

[Affected platforms]:
- Windows 7 32bit
- Windows 10 64bit
- Mac OS X 10.11
- Ubuntu 16.04 64bit

[Steps to reproduce]:
1. Open . 
2. Right click on the audio controls and select Hide Controls. 

[Expected result]:
- The controls bar is hidden, only the audio container is displayed (or the Hide Controls option does not appear in the context menu, as implemented in bug 1222669 for standalone audio files). 

[Actual result]:
- The control bars and the container are no longer visible on the screen. There is no way to show the controls again, the tab must be reloaded.

[Regression range]:
- It is not a regression, it reproduces since Firefox had support for playing Opus files 

[Additional notes]:
- For the standalone audio files, the problem is fixed by bug 1222669. 
- The page from this bug contains 2 audio files, isn't standalone. The problem should be also fixed for those files which are not standalone.
Priority: -- → P3

The current builds (60.5esr, 64.0.2, 65.0b11 and latest Nightly 66.0a1) are still affected by this behavior, is there any plan to fix this in the near future?

Reproducible in Windows 10 x64 on latest nightly 69.0a1 (2019-06-10) (64-bit)
Build ID 20190610093815
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:69.0) Gecko/20100101 Firefox/69.0

Reproduced in latest Nightly build 70.0a1 (2019-07-16).

Reproduced in latest Nightly build 71.0a1 (2019-09-10).

Reproduced in latest Nightly build 72.0a1 (2019-11-03) using windows 8.

Reproduced the issue in latest Nightly build 73.0a1 (2019-12-10).

I've tested this using the latest Nightly version 74.0a1 (2020-01-13) (64-bit) for Ubuntu 18.04.3 LTS and I’m able to reproduce the issue. Based on this I will mark firefox74 flag as affected.

This issue was reproducible on Windows 10 with Firefox Nightly version 74.0a1 (2020-01-14) (64-bit).

This issue was reproducible on Nightly version 75.0a1 (2020-02-18) (64-bits) on macOS 10.14


I was able to reproduce this issue on Ubuntu 18 with Firefox version Nightly 76.0a1 (2020-03-18) (64-bit). Marking that flag as affected.

This issue is reproducible on Nightly version 77.0a1 (2020-04-14) on macOS 10.15.

This issue is reproducible on Nightly version 78.0a1 (2020-05-27) on macOS 10.15

Reproduced in latest Nightly build 80.0a1 (2020-07-05) on the following test page:

Reproduced this issue on the latest Nightly build 81.0a1 (2020-08-03) on the following test page:

Reproduced in latest Nightly 82.0a1 (2020-08-31) (64-bit) Win 10.

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.