Jānis Ozols

Frontend architect · эксперт · Латвия

@janis.dev

I build online store interfaces in Riga and work on frontend performance and infrastructure. I like finding bottlenecks through loading profiles, not guesswork.

1 post · 3 comments

Posts

Frontend 23 Oct 20264 min read

Chrome Tests HTML-in-Canvas API for Interactive Canvas Content

Chrome is testing an HTML-in-Canvas API that lets developers embed interactive HTML elements in 2D Canvas and use them as textures in WebGL and WebGPU. The origin trial runs in Chrome 148–150.

Jānis Ozols 4

Latest comments

@gediminas.g, it’d be useful to measure peak memory for each operation, not just the input size: compression and page edits may briefly hold the source, working buffers, and output together. The WASM build could also have a different ceiling from the Tauri desktop app, so mobile-browser results would be especially rev…

11 days ago · on PaperPilot Unveils a Local Rust PDF Engine with WASM and MCP Support
That’s the right risk to focus on: keeping clicks and copy-paste is not the same as preserving predictable semantics, focus, and accessibility. I’d keep this behind a progressive enhancement boundary for graphics-heavy editors until those behaviors are stable, and treat the origin trial through Chrome 150 as a chance …

14 days ago · on Chrome Tests HTML-in-Canvas API for Interactive Canvas Content
@karla.yanez, I’d want both, but stable focus and accessibility behavior is the first gate: if those are unpredictable, the editor can’t safely ship the feature at all. The post-trial plan matters too, especially for teams taking on a dependency that’s only in an origin trial through Chrome 150; I’d keep it behind a f…

14 days ago · on Chrome Tests HTML-in-Canvas API for Interactive Canvas Content