923414 - Playback controls are fogged (unseen, but working)

Status: RESOLVED WORKSFORME

(Toolkit :: Video/Audio Controls, defect)

Description

[soshial]

Attachment: Unseen controls on Win7 x64 with hardware acceleration

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Firefox/24.0 (Beta/Release)
Build ID: 20130910160258

Steps to reproduce:

I open an mp3 file for playing.


Actual results:

Playback controls are not seen for me, although they are clickable and the music plays.

Comment 1

[[:Aleksej]]

Works for me with firefox-24.0.en-US.linux64 with an Ogg/Vorbis file, w/o hardware acceleration, and with or w/o JS; and with firefox-24.0.en-US.linux64 with that MP3 file.

Does it depend on whether hardware acceleration is enabled (Options → Advanced)?

Comment 2

[soshial]

It's hard to say. This happens only from time to time. I notice that "hardware acceleration when availible" was on the whole time. And also, this is on Windows. I'm not sure, whether these OS are comparable in this case.

Comment 3

[soshial]

The same thing happens with hardware acceleration turned OFF.

Comment 4

[soshial]

Attachment: Unseen controls on Win7 x64 without hardware acceleration

Comment 5

[(mostly gone) XtC4UaLL [:xtc4uall]]

Still an Issue?
Can you provide a link to a public example this happens with?

Comment 6

[soshial]

Still an issue on v26. For instance, this file: http://2.cdn.echo.msk.ru/snd/2013-12-20-osoboe-1908.mp3

Comment 7

[(mostly gone) XtC4UaLL [:xtc4uall]]

This is WFM against Firefox 26-29.

please provide/attach the "Important Modified Preferences" from about:support.

Comment 8

[soshial]

Attachment: Important Modified Preferences

NB! This bug reproduces approx. 1 out of 3 times.

Comment 9

[Jared Wein [:jaws] (please needinfo? me)]

Can you test this on tomorrow's Nightly build? Some fixes to the audio player have landed recently and that may fix this bug for you (notably bug 1222669).

Comment 10

[Jared Wein [:jaws] (please needinfo? me)]

Closing this as works-for-me as the reporter has not responded and this was likely fixed in the interim. Please reopen if you are still able to reproduce with the latest Nightly build.