3 ms·
In this case there Non-tech preview version of safari scored higher, due to a bug in the testing framework which was not correctly updating the tech preview ve
by syspec 5y ago
In this case there Non-tech preview version of safari scored higher, due to a bug in the testing framework which was not correctly updating the tech preview version used.
Yet they still used the tech preview number which was much lower, in their slides
That's why there's uproar, chrome dev tools team showed the lower score which was caused by a non-updating test framework and people ran with it
- magicalist 5y ago> due to a bug in the testing framework the "bug" is https://github.com/web-platform-tests/wpt/issues/31147 https://github.com/web-platform-tests/wpt/issues/31147 MacOS 11 isn't allowed(?) to be virtualized, so the Safari TP, which is tied to MacOS updates, couldn't be updated. > That's why there's uproar Was there an uproar? There were some objections from some Safari devs that they understood the difficulty in getting the latest number since the web platform test runner can't run the latest Safari Tech Preview (which they've also known for some time), but since the whole point of this was to show how browsers have improved their compatibility on this set of tests, it was hurtful and counterproductive to leave out their latest work. Chrome devs apologized and now we have this article, and it looks like the test runner will start running WebKitGTK for this set of tests so at least the Compat 2021 dashboard[1] will show the latest results. [1] https://wpt.fyi/compat2021?feature=summary https://wpt.fyi/compat2021?feature=summary
- sangnoir 5y ago> MacOS 11 isn't allowed(?) to be virtualized IANAL, but IIIRC, MacOS isn't allowed to be virtualized on non-Apple hardware