This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

ค้นหาฝ่ายสนับสนุน

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

เรียนรู้เพิ่มเติม

why does webGL 3d rendering work well in Firefox Developer Edition but not in Firefox Quantum (both latest versions)

  • 2 การตอบกลับ
  • 1 คนมีปัญหานี้
  • 1 ครั้งที่ดู
  • ตอบกลับล่าสุดโดย cor-el

more options

I am creating a 3D floorplan and find that Firefox Quantum (latest version) will not display it at all and provides a couple of error messages relating to resources and WebGL, however, when i visit the same url in Firefox Developer Edition the page works brilliantly.. the url works in Chrome, but Firefox Dev Edition is far superior with smooth and high quality rendering.

I have tried to disable all the Add-ons in the Quantum/default Firefox etc etc but nothing works.. so I wondered if there was a SIMPLE way to configure Quantum like Dev Edition that I can advise my clients.. so we can keep Firefox in the loop.

I am creating a 3D floorplan and find that Firefox Quantum (latest version) will not display it at all and provides a couple of error messages relating to resources and WebGL, however, when i visit the same url in Firefox Developer Edition the page works brilliantly.. the url works in Chrome, but Firefox Dev Edition is far superior with smooth and high quality rendering. I have tried to disable all the Add-ons in the Quantum/default Firefox etc etc but nothing works.. so I wondered if there was a SIMPLE way to configure Quantum like Dev Edition that I can advise my clients.. so we can keep Firefox in the loop.

การตอบกลับทั้งหมด (2)

more options

oops, I need to add one critical factor.. I am viewing the 3d in an iframe, which is the source of the problem..

more options

See also:

You can check the Web Console to see if content is blocked.