NOBODY is sitting down and validating the end-result from the perspective of a human user sitting in front of an actual device. What you're experiencing is the end result of all of this. Automated tests don't measure "jank", or inconsistent performance issues, Etc, etc.
Automated tests don't have funky hardware combinations. Automated tests use default, vanilla settings for the host OS. Automated tests are almost never set up for long-term testing for things like memory leaks, because they have to run fast.
Automated tests are literally blind to output color rendering testing that requires a physical monitor. If it ships in a working state, that's probably just a lucky accident, and a subsequent patch will break it for sure.Īll of the issues above are caused by automated test suites one way or another. It's all automated and those people have been summarily fired.Īny issue that is invisible to a DevOps pipeline is Not A Bug and will ship broken. The point I'm trying to get to is that in 2022 we've achieved this state of affairs where human beings don't do actual Quality Assurance any more as a job. But not quickly enough to prevent the automated test suites from passing.
Speaking of HTTP/3 in Firefox: I've had it permanently disabled because the early releases would leak about 10 GB of memory per minute and lock up the browser very quickly. But they will work with external displays! If you have a laptop with one of those hybrid Intel+NVIDIA GPU combinations, then HDR games don't work at all with the built-in display, they all report HDR support as N/A. Then it worked again after a few weeks when it updated.īut it might not be Firefox's fault, because Windows also seems to randomly turn color management off, or force it back to sRGB silently. Speaking of color: Firefox for a while just. Why? Because Microsoft employees test using Azure VMs, which.
Windows Server 2022 can't activate its license unless it uses the UTC time zone. We're back to 8-bit RGB arrays in sRGB only as the only option. As in, Microsoft literally removed a wide swath of floating-point color support along with the wide-gamut scRGB color space. The Win UI SDK regressed from WPF and lost all wide-gamut or HDR support at the API level (which probably explains the above). It kinda-sorta works for some things, sometimes, but most apps that used to work with HDR back in Windows 10 just can't any more and are forced to use SDR with sRGB gamut only. Windows 11 almost but not entirely broke HDR. I just got a new laptop, and the amount of things that get shipped totally broken is just crazy. I've spent the last 3 days angrily submitting bug ticket after bug ticket, including one for Firefox.
0 kommentar(er)
