I have a React app, created with ‘create-react-app’ (I also use jsdom NPM package), and for some reason, the application throws an error on load Only in Firefox (works fine in Chrome & Edge). Here is the error: After some Googling I found: “To enable SharedArrayBuffer in Firefox, go to about:config and set the javascript.options.shared_memory preference to true” (https://github.com/ggerganov/kbd-audio/issues/9) The
Tag: firefox
how do you install and run puppeteer for firefox
Hi I am doing some web automation. I am trying to open a url and I am getting a data URL error in chrome console so I am moving to firefox console to get around the no data urls opening in the chrome console issue. The problem is “npm install puppeteer-firefox” is not working to install puppeteer for firefox. How
“NetworkError when attempting to fetch resource.” only on Firefox
I’m doing a POST request from my frontend using fetch API. But when I tried in Firefox, it doesn’t work. In Chrome works fine. Here’s what I’m trying to do. Answer So, guys, here’s the solution. The problem was the time for refreshing the form, is refreshing before send it. To solve this, set to refresh the form on response,
Firefox: Service Worker: SecurityError: DOMException: The Operation is insecure
In app.js, I am checking the serviceWorker existence in navigator object and if available then registering the SW. When trying to register SW, I receive the below error in Firefox. I also made sure the service-worker.js file is under src directory. Checking my about:config in Firefox (version 59.0.2) I had service worker and storage api enabled. So that shouldn’t be
Intersection Observer API Fires callback even element is not in view
I am trying to find when the element is on screen(trying to implement the infinite loader). Bind the Observer for the last item in the list and listen, unfortunately in chrome 62 mac 10.10 , callback is firing even though the element which I am observing is not in the viewport. I could prevent it easily when I checked the
Whitelisting inline script with csp sha-256 in firefox
I can not get whitelisting by checksum to work in firefox (52.0.2, windows). Firefox supports content security policy version 2 according to caniuse, so checksumming should be supported. When chrome blocks an inline script, it prints the needed sha-256 to console. Adding it to the csp rules successfully whitelists the script. The checksum is also identical to the one calculated
Is it possible to display a custom message in the beforeunload popup?
When using window.onbeforeunload (or $(window).on(“beforeunload”)), is it possible to display a custom message in that popup? Maybe a small trick that works on major browsers? By looking at existing answers I have the feeling this was possible in the past using things like confirm or alert or event.returnValue, but now it seems they are not working anymore. So, how to
a href=javascript:function() in firefox not working
I tried using a href=javascript:function() in a button, with a function to execute it. It works in Chrome but it doesn’t work in Firefox. Firefox doesn’t alert and open blank tab. Anyone can help me? Below is button code Update I should have added that im using a live editor(profitbuilder) in wordpress to generate the page and button. There is
ERR_CONNECTION_REFUSED http://localhost:3000/socket.io/socket.io.js
Ciao, I’m implementing a webRTC many-to-many videoconferencing system, actually, I already did it, I am using socket.IO as signalling server, and everything goes super well, I am using EnterpriseDB Apache for serving my .html file on port (8081) and Node.js for serving socket.IO on port (3000), It is working like charm in localhost, no errors, My ISSUE is serving for
Prevent parent page from scrolling when mouse is over embedded iframe in Firefox
…without limiting the scroll inside the iframe or the need to specifically name/tag all scrollable elements. Imagine google maps widget embedded in parent page. When you zoom in the widget you don’t want the parent page to scroll, obviously. I thought an answer to my previous question solved the problem: While scrolling inside an iframe, the body doesn’t know anything