Bugzilla

This sounds like the same thing as bug 1675357.

Honestly it sounds like failIfMajorPerformanceCaveat: true used to not work, and now it's working.
The minimal testcase explicitly asks for `failIfMajorPerformanceCaveat: true`, which if you have non-accelerated compositing, will cause context creation to fail. (by design and by spec)

The last thing I need for clarity here is a copy of about:support for 82 on a machine where it's "broken" in 83, but worked in 82.

---

The answer for frustrated website *authors* is straightforward: Don't ask for failIfMajorPerformanceCaveat: true unless you *do* want context creation to fail for many many users. failIfMajorPerformanceCaveat has no other use besides this "bug", so don't ask for it if you don't want this behavior.

For frustrated *users*, the workaround is toggling "webgl.disable-fail-if-major-performance-caveat" to "true" in about:config.

---

We may be able to make this better:
* Point people towards webgl.disable-fail-if-major-performance-caveat in the console warning text we generate. Moderately technical users will then be guided towards the proper workaround this issue for themselves and others.
* Add a checkbox to the Firefox Settings pages to allow users to tell us how to handle this

@ken needinfo for FYI

This sounds like the same thing as bug 1675357.

Honestly it sounds like failIfMajorPerformanceCaveat: true used to not work, and now it's working.
The minimal testcase explicitly asks for `failIfMajorPerformanceCaveat: true`, which if you have non-accelerated compositing, will cause context creation to fail. (by design and by spec)

The last thing I need for clarity here is a copy of about:support for 82 on a machine where it's "broken" in 83, but worked in 82.

---

The answer **for frustrated website authors** is straightforward: Don't ask for failIfMajorPerformanceCaveat: true unless you *do* want context creation to fail for many many users. failIfMajorPerformanceCaveat has no other use besides this "bug", so don't ask for it if you don't want this behavior.

**For frustrated users**, the workaround is toggling "webgl.disable-fail-if-major-performance-caveat" to "true" in about:config.

---

We may be able to make this better:
* Point people towards webgl.disable-fail-if-major-performance-caveat in the console warning text we generate. Moderately technical users will then be guided towards the proper workaround this issue for themselves and others.
* Add a checkbox to the Firefox Settings pages to allow users to tell us how to handle this

@ken needinfo for FYI