After updating Firefox (Firefox 72.0) an error appeared: "The buffer passed to decodeAudioData contains invalid content which cannot be decoded successfully." Apps don't work, because of this problem with audio playback. Has anyone encountered such a problem? Thanks.
Got the exact same problem but here's a bit more info for anyone working on a solution. The latest updates of firefox work fine on IOS and Android, the problem is on windows 10. Here are a couple of educational resources that several of our school's reported as broken by the recent update (they work fine in chrome, safari and edge):
https://www.echalk.co.uk/Science/physics/spacecadet/SpaceCadet.htm
https://www.echalk.co.uk/ComputerScience/ComputerSystems/Memory/Moonlander/memoryMoonlander.html
For comparison, here is a rource that still works in Firefox:
https://www.echalk.co.uk/Maths/estimation/fractions/estimationFractions.html
All resource were built using the same libraries, notably createJS.
Related
I would like to ask about these images I found to be glitchy on google chrome.
I must confirm that none of these are intentional.
This started since I saw a glitchy image on my google classroom, here are some images I found to be glitchy. I don't seems to find a pattern from them.
Glitchy image on google classroom
How the google classroom image should look like (my friend's perspective)
Broken logos of chrome extensions (fullscreen)
Broken search icon
Broken pdf icon on web.whatsapp.com
It sometimes manages to fix itself though, I successfully took a screenshot of glitchy icons and the normal ones.
Search Icons, both normal and glitchy displayed at the same time
I've tried to delete images cache and even reinstalled chrome, none of them works to fix this problem.
Some information that might help narrow down the problem:
I've recently used this PC with a new SSD (I've used it for about a month now), which contains the chrome itself, and it works properly so far. I don't think this should be a problem with the disk. (please correct me if I'm wrong)
However, on the day this happens, I installed the React Devtool (I've deleted it though) (https://chrome.google.com/webstore/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi) and the Redux Devtools (https://chrome.google.com/webstore/detail/redux-devtools/lmhkpmbekcpmknklioeibfkpmmfibljd)
Can this problem be a bug on the chrome itself, or perhaps something related with skia? Should I report this as a problem to Chrome, or is this a problem on my end?
Information about my OS and Google Chrome (I'll provide more if it is required):
OS:
Edition: Windows 10 Pro
Version: 20H2
Installed on: 1/10/2022
OS build: 19042.1526
Experience: Windows Feature Experience Pack 120.2212.4170.0
Chrome:
Version: 98.0.4758.102 (Official Build) (64-bit)
Thanks
EDIT: Fixed, I changed from using GPU 0 to GPU 1 via settings, is this a graphics card compatibility issue?
GPU 0: Intel(R) HD Graphics 530
GPU 1: NVIDIA GeForce GTX 950M
Setting "Choose ANGLE graphics backend" (chrome flag) to "OpenGL" fixed the issue for me.
Firefox 56+ breaks Gamepad API across multiple windows/tabs
The application I am working on uses the Gamepad API to allow xbox controllers to be used to control video producing cameras. It supports multiple windows/tabs.
Everything worked great, but after upgrading from Firefox version 52 to 65 the controllers stopped working correctly when multiple pages were open. The update is necessary for video stability, so downgrading is not an option.
Worst case will update with the fixed Vesrion if Mozilla fixes the issue.
How to reproduce:
Running windows open Firefox version 56+
Open https://html5gamepad.com/
Connect a xbox controller (maybe any gamepad)
Observe that the controller is detected and that input on the gamepad is shown in the tester.
Open a second window and navigate to https://html5gamepad.com/
Observe the at the controller is not detected
Expected: The controller should be detected and inout should be shown in the tester.
If you downgrade below 56 or disable multiprocess using browser.tabs.remote.autostart this issue is not seen.
What I do know / have tried:
Have narrowed down the issue to Firefox version 56.0.0
Can reproduce the issue consistently with https://html5gamepad.com/
Can not reproduce with Chrome or Firefox 52
Turning off browser.tabs.remote.autostart does remedy the issue, but again, this is necessary for video stability and overall performance.
navigator.getGamepads in the second window seems to return an empty list
Tracking ff issue
https://bugzilla.mozilla.org/show_bug.cgi?id=1538805
and ff issue https://bugzilla.mozilla.org/show_bug.cgi?id=1529850
The issue is one per website
Before this is marked as a duplicate. I know this is a similar question as Is there a way to use the HTML5 Gamepad API with multiple windows or tabs in Firefox? but there has been no movement on that issue and it was very specific.
TLDR: FF v56+ with multiprocessing enabled breaks the Gamepad API when used in multiple windows. Any workarounds or fixes?
As of Safari 11, they have started supporting WebRTC apis natively.
In my web application I am using navigator.mediaDevices.getUserMedia to get control of the microphone.
I noticed that, only in Safari, when my code calls getUserMedia, the sound on my computer gets low then comes back up to normal volume after a second.
I have tested this on another website: https://simpl.info/getusermedia/
When I loaded the website, I did not see the issue..
The site above only requests for video, but the code is very simple and not minified. I put a breakpoint right where it calls getUserMedia and added the constraint for audio and I was able to reproduce the issue.
Has anyone else had this problem? I am unable to find anything online describing this issue.
I am running Mac OSx El Capitan. I know I am out of date but people have told me that this happens on Sierra as well.
The same on High Sierra.
My guess is they try to avoid audio spikes or to go easy on the echo canceler.
I'm testing mediaelement.js with various OS (Win XP and 7 so far) and browser combinations (Chrome, FF, IE8, Opera) before using it on my own website. Those combinations seem great but after hours of effort I can't get Safari to work well enough under Windows XP SP3 to do a true test of whether mediaelement.js works in Safari under Windows XP (Safari normally doesn't respond when visiting web pages with or without mediaelement).
Forum posters say that one shouldn't bother to try to make Safari and XP work together but my users worldwide use many combinations of OS and browser so I need to know whether to warn them off from trying to use my mediaelement-based pages with Safari and XP.
Can someone please confirm or deny that Safari on a Windows XP PC can play the video on http://mediaelementjs.com ? I would be most grateful.
I also tried this running an XP VM with all the latest updates. It worked with Safari 5.1.5 and I also upgraded it to 5.1.7 and both played the video without a hitch.
I found an old Win XP PC in the attic, installed Safari 5.1.7 and it handled the video on http://mediaelementjs.com fine.
I've been having this issue too. It's only on Safari on Windows. So far, I've had issues with Safari telling me that certain MediaElement functions don't exist:
TypeError: 'undefined' is not a function (evaluating 'this.pluginApi.loadMedia()')
It's obviously an issue with the Flash fallback and it occurs after calling .load(). It seems like a bug in MediaElementJS because that is an internal function.
I started setting the source like this:
var player = $('#wp_mep_1')[0].player.media;
player.src = 'video_url.mp4';
and then for Safari, or the Flash fallback, I had to manually change the flashvars after clicking to get the video to update:
$j('#me_flash_0').attr('flashvars','id=me_flash_0&isvideo=true&autoplay=false&
preload=none&width=480&startvolume=0.8&timerrate=250&flashstreamer=&height=270&
file='+video_urls[slider_position]+'.mp4');
Microsoft recently done this update for flash in IE10
http://support.microsoft.com/kb/2758994
after which our product, that was working fine across all browser stopped working totally in IE10.
We have a flash WebUI which connects to Desktop AIR App using LocalConnection class.
There are now exceptions and no information on this in web.
And product continues to work fine in all other browsers so that's not the code's issue.
The only similar issue that i found is here - http://forums.adobe.com/message/5103110
Has anyone else encountered something like this? or any ideas on how it can be solved?
I would very appreciate any advice