6 ms·
Got "Infinity" after testing my Firefox Dev Edition 123b9. Is this because of my FF config because my browser is perhaps blocking something (e.g. canvas, finger
by murat124 3y ago
Got "Infinity" after testing my Firefox Dev Edition 123b9. Is this because of my FF config because my browser is perhaps blocking something (e.g. canvas, fingerprint, etc) or any result north of 140 is considered infinity?
- julienwaj 3y agoDo you see anything (errors or something else) in the web console?
- julienwaj 3y agoPlease file a bug there if necessary => https://github.com/WebKit/Speedometer/issues/new https://github.com/WebKit/Speedometer/issues/new :-)
- dist-epoch 3y agoI also got Infinity, on Firefox 123.0.1, with a bunch of privacy extensions. There is only one warning in the Console: Ignoring ‘preventDefault()’ call on event of type ‘wheel’ from a listener registered as ‘passive’. react-dom.production.min.js:29:112
- gruez 3y ago>because my browser is perhaps blocking something (e.g. canvas, fingerprint, etc) or any result north of 140 is considered infinity? I vaguely remember there's a privacy protection that rounds timer information. eg. all timers get rounded to the nearest 100ms. If you have a bunch of tests that take less than 100ms to complete, those tests might seemingly complete at the same time they start, which causes them to have infinite score.