Julien Wajsberg

> Loooking good. I guess we can redo the formatting now that we've released? yeah, I was waiting to see if there was some interest before doing more work :-)

I rebased and refreshed all affected benchmarks. On my Linux: Firefox Before:  Firefox After:  Chrome Before:  Chrome After:  (I don't have a Mac so I can't...

But I don't understand why one single substep being at 0 would yield an Infinity result. I'm not great at statistics, but I smell something fishy here.

(update: I got it wrong, I rewrote the comment) > But I don't understand why one single substep being at 0 would yield an Infinity result. The problem isn't a...

Note: I also noticed errors with NaN values in the SVG rendering of the Details view, I believe this comes from the same issue.

I find our score computation very difficult to follow, where we do the same thing in different ways in different files: benchmark-runner.mjs vs metric.mjs vs Statistics.mjs, with no clear comment...

Yeah indeed, 0 is an absurd number in this case. Is it practical to ignore the test instead of failing generally ?

``` Cross-Origin-Opener-Policy: same-origin Cross-Origin-Embedder-Policy: require-corp ```

One can see the webpack config used by vue like this: ``` ./node_modules/.bin/vue-cli-service inspect --mode production 2>&1| less ``` Here we clearly see that the absolute directory is used everywhere....

This bug tracks the implementation of the WakeLock API in Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1589554