Molire, I haven't heard back from you.

is this all the measurements: i.e: the top 8 results (down to viewport) or just some of them

It would be cool if you could confirm that it was just the two css and the two matchMedia lines that differed, but I'm now 100% sure this is the case. I made some changes (see the link below) so people don't get confused, so thanks - although the site is not aimed at the average person. It's also made me think of a new attack vector.

Here is a pic and a tiny bit of text * https://github.com/ghacksuserjs/TorZillaPrint/issues/45#issuecomment-562641910

When you said my measurements were out by 1px, it cannot mean all of them (asking JS for window.innerHeight etc is not hard and basically codewise you can't mess it up and it can't lie, the JS that is). And the fact it is only ever 1 pixel means it has to be only the css @ media results (which are also used in the matchMedia JS). I've also reviewed and eliminated the possibility of timing issues to my own satisfaction.

In the pic you can see my android phone results, where because of the DPI, 1800 is not exact. window and screen properties via JS will report 1801, css min-width and min-device-width will report 1800. This is entropy, which I am leveraging by design. This is how fingerprinting works, by exploiting implementation of APIs

None of the other test sites listed uses these methods: except canvasblocker and if you count Matt's css PoC, then there's that.

So if you want to compare apples to apples: then you can't really blanket say my figures are wrong when it's not even the same thing being measured - my mistake for the output being misleading for you - as Matt says:

https://matt.traudt.xyz/posts/how-css-alone-YF4ciVY6.html

Remember that I caution against reading too much into the results of a fingerprint test, but if you know what to do with this information ...

Hope you read this and reply and confirm for other readers (and/or edit your post about my "inherent inaccuracy").