Shockwave Flash issue in newer versions of Firefox
I would like to report an issue with Shockwave Flash plug-in that appeared in latest versions of Firefox, Firefox 46 is the last one which does not suffer from it, that has been discouraging me for a long time from updating the browser. Actually, the plug-in is still needed on some websites, such as Spotify, but it also prevents the browser from playing mp3 previews on other sites, I know about djshop.de, for example here < https://www.djshop.de/Style-News-Download-electro-house/ex/s~newsByStyleMP3,u~145/xe/electro-house.html >. If it you disable it, it works again, however, since there are no such problems in older versions of Firefox (46 and older), it leads me to believe the bug is in Firefox and not in the plug-in itself. The issue concerns the 64 bit browsers, I am not sure if it concerns the 32 bit ones too, but if I remember correctly when I tested it few months ago, Firefox 47 32-bit was still okay unlike its 64-bit counterpart.
Всички отговори (2)
With the Shockwave Flash plugin disabled, I get the HTML5 media player that plays an MP3 file.
audio: id = "jp_audio_0"; src = "https://d2k8y339bkfb24.cloudfront.net/preview/65/60/8610012800.mp3"
With the Shockwave Flash plugin enabled I get the JPlayer that uses a Flash player.
embed: src = "/gfx/Jplayer.swf";
Did you make sure that the Shockwave Flash plugin is enabled? Check the Lego block icon at the left end of the location/address bar.
Yes, it is enabled, I have just tried to install the latest 32-bit version of Firefox (51.0.1) and everything is fine there. Actually, if I click on the lego block icon and block the plugin use on the page, it starts doing the same thing as the 64-bit browser, i.e. after clicking on the 'play sound' icon it opens the waveform seekbar (png) but does not play the sound. In the 64-bit version enabling or disabling the plugin by clicking on the lego block icon does not change anything there. I would think that the plugin might be incompatible with the 64-bit browser or rather might contain a bug if it had never worked in it, but that's not the thing, it worked well until Firefox 47 where the issue began.