I would use it to render HTML elements such as inputs or a website in videos. Even though HTML is powerful the control over every pixel is important for high quality videos.
dvh 1 hours ago [-]
Wouldn't it make more logical sense to add canvas to html elements? I.e. checkbox.getContext("2d").fillRect(...)
azangru 1 minutes ago [-]
Not if you need your html to adapt to the shape of a 3d object drawn in the canvas.
What you described is the CSS painting api (part of CSS Houdini)
aroman 54 minutes ago [-]
I guess there are uses for that, but as a web game developer, that wouldn’t really help me. The killer feature is input and text rendering.
51 minutes ago [-]
avaer 1 hours ago [-]
Back in the WebVR days the sentiment was we can never do this because security.
In my experience with standards bodies/Chrome, anything outside of the owning company's product goals is "no, because security", and then then they flip-flop on that when the browser feature becomes a dependency for something an internal team is working on (which happened many times with WebVR, now WebXR).
So I'm curious what is Google working on that has this as a dependency, now that they've 180'd on it?
bawolff 20 minutes ago [-]
"Security" is usually not a binary, but how much money you are willing to spend to figure out a way to do it securely. It shouldn't be surprising that chrome spends more resources on things that have a business case than things that do not.
thomasikzelf 1 hours ago [-]
This had to do with leaking privacy sensitive information such as visited links by reading back pixels from a rendered <a>. They fixed this with a concept they call "read-back-allowed rendering"
43 minutes ago [-]
chews 10 hours ago [-]
Yo dog, we put a DOM in your Canvas in your DOM.
Rendered at 08:08:43 GMT+0000 (Coordinated Universal Time) with Vercel.
Related bunch of comments from that time: https://news.ycombinator.com/item?id=48201222
What you described is the CSS painting api (part of CSS Houdini)
In my experience with standards bodies/Chrome, anything outside of the owning company's product goals is "no, because security", and then then they flip-flop on that when the browser feature becomes a dependency for something an internal team is working on (which happened many times with WebVR, now WebXR).
So I'm curious what is Google working on that has this as a dependency, now that they've 180'd on it?