Weirdness With Temp-Allowed <audio>

[barbaz]

NS 2.6.9.37rc1, SeaMonkey 2.35, Linux x86_64

STR:
1) go to http://www.forcexl.com/post/Best-Of-Valentin.aspx, make sure nothing from forcexl.com is (Temp-)Allowed
2) un-block the audio by clicking on the placeholder
3) click the pause button

Expected results: audio is paused

Actual results: nothing happens. The only way to pause is to right-click somewhere not in the "seek" area & click the "Pause" menu item.
Once the audio is paused, clicking the play button will play only a tiny amount of the audio - to resume it properly, must right-click & click the "Play" menu item.
Oh, and after it's been fiddled with along these lines, seeking becomes a play/pause button? Actually, everything BUT the play/pause button is a play/pause button!
Reloading the page manually does *not* bring it back to normal.

And in a test profile with NS disabled & javascript.enabled set to false, this issue is not present; enabling NS brings this issue back regardless of browser's JS enabled setting.

[therube]

I didn't look, is it Flash?
Seem to recall a bug on the FF end that you had to hit some button twice, kind of thing. Sounds like what you're saying.
Don't know Bug # offhand, or even where it may have crossed my path?
So might check FF 40, without extensions, & see if the same might occur?

[barbaz]

I didn't look, is it Flash?

No, it's HTML5 audio element, no Flash.

So might check FF 40, without extensions, & see if the same might occur?

Can't atm, sorry.
What I will do though is see if the same happens in a completely clean profile with only NS, in SeaMonkey 2.35.

EDIT In case I didn't make it clear in the OP, without NS all this works exactly as expected.

[barbaz]

What I will do though is see if the same happens in a completely clean profile with only NS, in SeaMonkey 2.35.

Confirmed there too. I have also verified that this happening regardless of whether the "default" extensions are enabled.

[therube]

OK, confirmed.

[therube]

? viewtopic.php?p=78808#p78808

Prior to looking at the issue, your description sounded like some sort of FF Bug I thought I read about, where Flash (video) was requiring a double click of Play/Pause to affect an action.

In any case, when I actually did look, I was able to confirm the issue you posted.

[therube]

your description sounded like some sort of FF Bug I thought I read about

Bug 1173848 - Play button indicates wrong state , and there is a need to click twice on the play button to start playing if media.autoplay.enabled = false

[barbaz]

It happens also with <video>
URL: http://www.quirksmode.org/html5/tests/video.html