2 ms·
According to MDN Safari clamps it to 4 or 8, but Firefox does not: https://developer.mozilla.org/en-US/docs/Web/API/Navigator/hardwareConcurrency https://develo
by daemonologist 1y ago
According to MDN Safari clamps it to 4 or 8, but Firefox does not: https://developer.mozilla.org/en-US/docs/Web/API/Navigator/hardwareConcurrency https://developer.mozilla.org/en-US/docs/Web/API/Navigator/h...
I always found it annoying that CPU information was widely available and precise while memory information was not - it's clamped to 0.25, 0.5, 1, 2, 4 or 8 GB. If you're running something memory-bound in the browser you have to be really conservative to avoid locking up the user's device (or ask them to manually specify how much memory to use).
https://developer.mozilla.org/en-US/docs/Web/API/Device_Memory_API https://developer.mozilla.org/en-US/docs/Web/API/Device_Memo...
- Jap2-0 1y agoI was thinking of https://bugzilla.mozilla.org/show_bug.cgi?id=1984333 https://bugzilla.mozilla.org/show_bug.cgi?id=1984333. Looks like that's only active when certain fingerprinting protection settings are on.