News for hackers. Stuff that matters.
Re:Firefox takes a bite out of the canvas ‘super cookie’ by vanderZwan on Monday October 30, 2017 @11:31AM (#15585713)
This "breaks" some libraries with a legitimate use of reading the canvas data, like favico.js[0] (although arguably, the only reason favico.js has to read the canvas data is because the favicon API is stuck in the nineties)

[0] https://github.com/ejci/favico.js

Re:Firefox takes a bite out of the canvas ‘super cookie’ by maccard on Monday October 30, 2017 @02:18PM (#15587505)
I have to say, if losing this “feature” is the worst that happens, I’m totally ok with that.
Re:Firefox takes a bite out of the canvas ‘super cookie’ by phkahler on Monday October 30, 2017 @04:35PM (#15588640)
That's how I feel about most browser "features" these days. What ever happened to plain old static sites? Why does everything need little floating and collapsing stuff all over? And fade-in imagery and all that nonsense.
Re:Firefox takes a bite out of the canvas ‘super cookie’ by BenjiWiebe on Monday October 30, 2017 @06:15PM (#15589433)
And even collapsing, fading, and floating can be done with CSS alone. No JavaScript needed.
Re:Firefox takes a bite out of the canvas ‘super cookie’ by vanderZwan on Monday October 30, 2017 @04:30PM (#15588606)
I agree, the only reason favico.js needs that is because favicons can only be set through a link, which means you need to pass a data URL, which means you have to read the data out of a canvas.

I don't see many other situations where that applies.