3 ms·
My understanding was that browser makers looked at the CSS custom filter spec and decided they were too difficult to implement securely[0]. On one hand, I defi
by danShumway 3y ago
My understanding was that browser makers looked at the CSS custom filter spec and decided they were too difficult to implement securely[0].
On one hand, I definitely appreciate that, I'm glad to see a feature abandoned if it's being abandoned because it's impossible to do it safely. On the other hand... I wanted CSS custom filters so much and I still regularly think of things I could have done with them :)
[0]: https://lists.webkit.org/pipermail/webkit-dev/2014-January/026098.html https://lists.webkit.org/pipermail/webkit-dev/2014-January/0...
- autoexec 3y agoThere's already enough problems with CSS and what it can do that I want an add-on which either disables it entirely, or allows only a tiny subset of it. I can appreciate a clever use of CSS the same way I can with JS but for my day to day browsing I don't want either being able to do whatever it wants because far too often what websites use it for is user-hostile.
- danShumway 3y agoCSS shaders are the kind of feature that I would get a ton of use out of for specific projects, and would also very likely either turn off entirely or at least put behind a permission in my own personal browser. I get why they're likely a bad idea, I'm not saying they should be implemented. It's very likely the right decision to get rid of them. I just mean... I want them XD