Clearly the browser is telling the web server about its capabilities, and the web server then sends the appropriate version of the HTML.
The <embed> tag in the HTML delivered to FF on XO invokes the VLC plugin (the user is prompted to activate the VLC Plugin), while on the other platforms, the <video> tag is used.
The first thing we found was that the HTML delivered to the browser is quite different depending on the platform, even for the same version of FF.
I think the ALSA / Pulse Audio thing may be something of a red herring, because there are sites where FF on XO will happily play audio, and specifically mp3 files.
Regarding the sound issues, we have done some more investigation on this.
Hi AdamAt present I am mainly working with FF26 out of the repo because it is correctly configured for XO re screen sizing etc, and the behaviour in relation to sound seems to be the same as FF 50.
As an aside, the performance of vanilla FF50 on XO-1.5 seems a bit sluggish compared to FF 26, and it is prone to crashing. Hopefully this can be sorted out in time.
So sound is basically working.
We looked at the various sites with Inspector in FF, on both the XO -1.5 platform and on FF running on Ubuntu and Windows.
On the robbbenson page which has a simple link to an mp3 file, the HTML code looks like this:
On FF on Ubuntu, Inspector shows
<video autoplay="" controls="" style="height: 28px; width: 66%;"></video>
On FF (ver 26 or ver 50) on XO, Inspector shows:
<body marginwidth="0"; marginheight="0">
<embed height="100%"; width="100%; name="plugin";
src="http//robbbenson.com/01%20Eve.mp3" type="audio/mpeg"> </embed>
The HTML sent to FF/XO invokes the VLC plugin and so the sound from the mp3 file plays happily.
Example 2.On the w3school Audio page, the HTML uses the <audio> tag and includes lines for both mp3 and ogg versions of the sound files.
When you run the example you can edit the html. If you edit out the .ogg line and then the sound will not work.
The FF/XO browser in this case can not run the mp3 file using the <audio> tag, but it can run the ogg file, so the site works ok on the XO.
On the ReadingEggs site the HTML is again different depending on the platform:
On FF Ubuntu the HTML uses the <audio> tag with only mp3 files provided.
On FF XO the HTML attempts to use a FlashAudio plugin, but sound does not work:
<div id="JSFlashContainer"; class="JSFlashContainer"; type="application/x-shockwave-flash" data="/soundjs/FlashAudioPlugin.swf"; ...
<object id="flashAudioContainer"; ... type="application/x-shockwave-flash" data="/soundjs/FlashAudioPlugin.swf"
style ... ></object></div>
So the FlashAudio plugin obviously does not work for playing mp3 files on the XO.
This leads me to think that the problem may lie in the configuration of FF on XO, specifically in how it tells the web server what its capabilities are for rendering sound.
I suspect that if the HTML from the RE site invoked the VLC plugin rather than the FlashAudio plugin, the sound on the RE site would work.
On Sun, Jan 8, 2017 at 1:45 AM, Adam Holt <[hidden email]> wrote:
Devel mailing list
But disabling it on the FF XO causes the site not to load the interactive picture.
A followup on the RE site.Disabling the Shockwave Flash plugin on FF Ubuntu does not affect the operation of the RE web site.
So clearly this plugin is not essential to the operation of the site.
On Mon, Jan 9, 2017 at 8:34 AM, T Gillett <[hidden email]> wrote:
Devel mailing list
|Free forum by Nabble||Edit this page|