Hello! I'm having an issue with sound and images showing up/playing on one of the sites that we utilize. On the same pc, sound an images work fine in IE11, Edge, Firefox (latest), Chrome (latest), and an internal build of Chromium. Am I missing something in the SEB config? Thanks!
You have to send us a link, demo login if necessary and step-by-step instructions how to reproduce the issue, otherwise we cannot help.
SEB 2.2 is using Firefox 52ESR (last compatible version with SEB 2.x), so you could test if the site works with that: https://www.mozilla.org/en-US/firefox/organizations/all/
Flash and other plugin contents might create issues in SEB.
Thanks for the reply. Unfortunately, I don't have a demo login that I can
share at the moment. I tested the site with the 52ESR and the site
performs as expected. (on same pc)
Anything else I can try from a seb config perspective?
Thanks!
On Tue, Aug 14, 2018 at 10:21 AM, Daniel Schneider danschlet@users.sourceforge.net wrote:
Related
Support Requests: #37
Test if the problem still persists when you switch off the kiosk mode: SEB Config Tool / Security / Kiosk Mode: None.
I could imagine that Firefox could theoretically use a helper process to output some sound/images. With Flash contents it was a bit similar (using a process plugincontainer or similar). SEB's kiosk mode might block some helper processes.
Otherwise you can research if some of the Firefox settings which you can find when you enter "about:config" in its adress bar could be the reason why particular media file types don't get played/displayed. The Firefox instance embedded in SEB is running in a XUL runtime mode, in which many of these Firefox settings have another default value than if Firefox is run standalone.
What exact kind of media types are not showing up/playing? Are they not displayed/played at all or not correctly?
We were not aware of similar problems, so we really can't help you if you don't provide us with more detailed information. Maybe the source code of the media embedding tags or player from your web page could help. But as I said before, mostly we can only help with problems we can reproduce and debug ourselves.