(In reply to Jeff Gilbert [:jgilbert] from comment #18) > After bug 1680595, it should be more clear to (power) users what they can do > to mitigate this. > > Functionality here is, I think, working as intended now. Unfortunately the > specified behavior causes certain websites (which arguably may have made poor > choices) work worse for our users, whereas before things were maybe slower > than they could have been, but otherwise functional. > > With that in mind, since we're now following failIfMajorPerformanceCaveat > spec properly, it's causing breakage. This bug is tracking the user > pain-point. In order to solve the user pain-point, we might ditch > failIfMajorPerformanceCaveat as accidentally-user=hostile for the time being. > > Two choices: > 1. Call these bad websites, and try outreach/education > 2. Re-evaluate the failIfMajorPerformanceCaveat mechanism entirely
Is there a bug/explanation somewhere of what behavior changed with failIfMajorPerformanceCaveat in FF83? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905054 Title: Firefox 83 Breaks WebGL To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
