Finding new a fingerprinting mechanism in JavaScript is like finding a new memory corruption bug in the web browser engine.

They are always going to exist for architectural reasons, some are worse than others, and the really bad ones are likely kept nice and secret while they are actively exploited. In other words, I'm not surprised in the slightest, but I'm glad that this is out in the open now.