Comment by Wowfunhappy

This wasn't really the point of the article, which in fact says the workaround was patched in Chrome 118.