| ▲ | The HTML-in-Canvas API origin trial(developer.chrome.com) | |||||||||||||
| 28 points by andrewstuart 12 hours ago | 10 comments | ||||||||||||||
| ▲ | chrismorgan 40 minutes ago | parent | next [-] | |||||||||||||
(May 2026.) Related bunch of comments from that time: https://news.ycombinator.com/item?id=48201222 | ||||||||||||||
| ▲ | dvh an hour ago | parent | prev | next [-] | |||||||||||||
Wouldn't it make more logical sense to add canvas to html elements? I.e. checkbox.getContext("2d").fillRect(...) | ||||||||||||||
| ||||||||||||||
| ▲ | prathje 26 minutes ago | parent | prev | next [-] | |||||||||||||
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. | ||||||||||||||
| ▲ | avaer 2 hours ago | parent | prev | next [-] | |||||||||||||
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? | ||||||||||||||
| ||||||||||||||
| ▲ | chews 11 hours ago | parent | prev [-] | |||||||||||||
Yo dog, we put a DOM in your Canvas in your DOM. | ||||||||||||||
| ||||||||||||||