22 points andrewstuart 11 hours ago 6 comments
chews 10 hours ago | parent
Yo dog, we put a DOM in your Canvas in your DOM.
avaer 1 hour ago | parent
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?
thomasikzelf 45 minutes ago | parent
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"
dvh 43 minutes ago | parent
Wouldn't it make more logical sense to add canvas to html elements? I.e. checkbox.getContext("2d").fillRect(...)
aroman 31 minutes ago | parent
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.
chrismorgan 10 minutes ago | parent
(May 2026.)
Related bunch of comments from that time: https://news.ycombinator.com/item?id=48201222