Website Collapsed Web Audi Autoplay Policy
My website is suddenly collapsed i have this warning in my console. Please help me how to fix this issue.
The Web Audio autoplay policy will be re-enabled in Chrome 71 (December 2018). Please check that your website is compatible with it.
See also questions close to this topic
Browser render hook
Do browsers provide any pre-render hook where you can apply changes to styles of DOM elements before they are rendered?
For example, I might want to change the color of anything that is red to green
- Scanning the DOM and checking the computed styles of each element and overriding stuff. This works but if elements change dynamically, we have to repeatedly scan for changes which might be heavy
So does such a browser hook exist? If not, what alternate approach would you recommend?
Google Chrome Licensing API returning 500 error
I'm trying to provide free trial for my chrome extension using Google Chrome Licensing API. I'm following the steps mentioned in their documentation here. I'm taking the code in this answer as reference. I have followed all the steps correctly but still I'm getting 500 error. This is driving me crazy from last couple of days. Any help is appreciated!
gatsby-plugin-offline causing site to hang?
I'm testing my Gatsby site and have found a series of actions that cause it to hang in the browser. By "hang" I mean the browser is trying the load the site, the screen is blank, and the progress bar gets to about 75% and stops.
I am using gatsby-plugin-offline and suspect that its an issue with the service worker however, it is difficult to know for sure.
I have only been able to reproduce this hanging behavior on Android using Chrome. Chrome on the desktop doesn't have any issues nor does Firefox on Android. I think it has something to do with the way Chrome resumes.
Steps to reproduce
- Open Chrome
- Navigate to the site directly by typing url
- Kill Chrome
- Reopen Chrome
When I reopen Chrome, it tries to reload the site since it was open when I killed the app and this is where it hangs.
If I wait long enough (about 5 minutes) the site stops trying to load but the screen is still blank. It seems to hit some sort of timeout. At this point I am able to view the console through the remote debugging tools in Chrome on my desktop. Before this point, while it is still hanging, I can connect to the phone with the remote debugger but there is no browser detected which is partially why this has been so difficult to figure out. When I look at the console in the remote debugger it shows that a handful of resources have failed to load. They are not always the same ones that fail however some common ones include the following:
All four of these items are in the cache as well as present on their respective host. The first three items are configured as precache items for WorkBox.
Final notes: There is nothing in the network tab of the debugger, just what I mentioned above from the console. If I refresh the site while it is hanging, or anytime, it works. Refresh always works, it's just when Chrome first opens that the site hangs.
Really strange stuff.