3 ms·
I thought this was some crazy CSS syntax I've never seen before: background: @shaders( fragment { } vertex { } texture { } ); Search
by esperent 10mo ago
I thought this was some crazy CSS syntax I've never seen before:
background: @shaders(
fragment { }
vertex { }
texture { }
);
Searching around just leads back to this blog though [0]. It would be amazing if this was real syntax, but I guess security reasons would probably make it a no-go for general use.
Indeed, there was an old CSS Shaders feature (in Chrome, behind a flag) behind from way back around 2013 [1]. Unclear if there's been any development since.
[0] https://yuanchuan.dev/add-shaders https://yuanchuan.dev/add-shaders
[1] https://developer.chrome.com/blog/introduction-to-custom-filters-aka-css-shaders https://developer.chrome.com/blog/introduction-to-custom-fil...
- anewhnaccount2 10mo agoLooks like it's an extension offered by this https://css-doodle.com/ https://css-doodle.com/
- esperent 10mo agoYeah, good catch. yuanchen.dev is the creator of that, I guess.
- Etheryte 10mo agoHere's hoping this will never come to browsers because this would become an endless pit of fingerprinting loopholes, similar to canvas and other related APIs.
- circuit10 10mo agoI think browsers can already block sites from reading image data from images embedded from other domains so maybe you could use the same logic here Also WebGL/WebGPU do exist already although I guess that’s easier to disable
- scotty79 10mo agoI eagerly await times when random website's CSS can mine crypto on my GPU.