4 ms·
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 c
by vanderZwan 9y ago
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 https://github.com/ejci/favico.js
- maccard 9y agoI have to say, if losing this “feature” is the worst that happens, I’m totally ok with that.
- vanderZwan 9y agoI 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.
- phkahler 9y agoThat'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.
- BenjiWiebe 9y agoAnd even collapsing, fading, and floating can be done with CSS alone. No JavaScript needed.