So recently I've noticed that I'm getting the error
THREE.WebGLRenderer: Error creating WebGL context
while trying to render a 3D model from a .glb file on Firefox 100
I am almost certain that this is not something to do with my own implementation, as browsing sites with similar feature show that all of them are broken too.
For example,
https://skinbaron.de/en/3dviewer
https://3d.cs.money/item/cxih4kC
https://buff.163.com/market/csgo_inspect/3d?assetid=25633198752
These links work on Chrome, at least on my current build 101.0.4951.54.
Does anyone have an idea whats going on?
Related
I wanted to test Three.js for a new project and imported it together with some example code.
In Firefox however the canvas with the three.js stuff doesn't show up and I get the error & warnings that you can see beneath. I guess the warnings appear because the WebGL context was not created correctly in the first place however I don't know what would go wrong there.
I don't know what could be the problem as the code runs fine and without warnings/errors in Chrome.
Both browsers were tested on an openSuse machine if that could play a role.
Thanks you for any hints on what could be wrong here!
Hey So I'm trying to design a gallery website, And I'm still a beginner
so I'm working through these problems however this problem is really something that i've never seen
The file that loads up in firefox loads up json from a local server.
I've modified the json file in the server but firefox however keeps showing me the same data over and over.
However the same file when opened in chrome opens up and shows me exactly what I want it to show
I'm quite baffled by this problem.
Firefox is most likely caching the result from the server to reduce load times. Try clearing the browsers cache and see if that fixes the issue.
I have been working on an A-Frame demo (code on Github). There seems to be huge performance difference when I run my project in different browsers. I am only getting <10fps in Chrome when I am getting a solid 60fps in either Firefox or Safari. Does anybody know what is causing this performance drop? I need to use Chrome for its SpeechRecognition API, for SpeechRecognition does not work in Firefox for the time being.
The default sky is too heavy, try setting segmentsHeight and segmentsRadius to a very small number.
This problem has been covered many times but none of suggested solutions worked for me so I decided to post this question again with a link to my site.
Please, check a sample webpage: http://miejska.tv/sinfonia-varsovia-zamienia-noc-w-dzien,wywiady,65.html
In chrome everything works 100%, all the time. The JWplayer shows up on the page, files are loaded and played correctly. In Firefox 90% of the time the JWPlayer shows up in half with an error message "error loading player. no playable sources found". Similar situation is with IE. Though problem occurs less often and after page refresh everything works ok.
I have updated the browsers and played with their settings, including change of safe mode of flash in Firefox. In vein.
Maybe there is some other code on the page that causes conflicts with JWPlayer. Maybe the problem lies somewhere else.
Please, have a look and help. Otherwise I'll have to switch to other player as Firefox in my country shares 50% of the market yet.
Witold
This is a really weird problem that appeared in the recent version of Chrome.
I have a huge app that loads hundreds of stylesheets (in dev mode). When the page loads, obviously all styles are applied but background images are missing!
If I just do nothing and wait, suddenly the images start loading randomly...
Using dev tools I checked the network tab to see if the images are requested.. but no, just a few of them appear in contrast to the previous version of Chrome.
Does anyone know if any kind of optimization has been added in Chrome that makes images load lazily? Obviously that implementation is buggy and does not consider a page with a lot of stylesheets!
This problem does not affect the app in production, where all the stylesheets are packed and reduced to just ~10.
Tested on Linux and Windows 7
I had a similar problem with our web site on Chrome 27.0.1453.93 and 27.0.1453.94. It turns out that Chrome seemed to think that all of our .gif images were corrupt. They wouldn't render in Chrome but they would render fine in IE, Firefox, and older Chrome versions.
I'm not sure what the underlying issue was, but I opened the images in Photoshop and re-saved them and now it works fine.