You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since there are multiple ways to render on the web, including inserting e.g. an svg into the page, it seems to me like it would be more generic to give graphics crates a Node or something, and then let them create and insert an inner element?
Or maybe there's something I'm missing here?
The text was updated successfully, but these errors were encountered:
WebGL and WebGPU both work with canvases, and expect the canvas to already exist somewhere (in memory as an element or offscreen canvas, or a node in the DOM).
People can create canvases ahead of time to style them, insert them at the right place at the DOM, attach event handlers, etc. so it doesn't really make sense for the graphics crate to take on the responsibility of creating it and surfacing ways to do all of these things.
We could also have handles for SVGs or other elements, but in practice this isn't very useful for the places raw-window-handle is currently used.
Since there are multiple ways to render on the web, including inserting e.g. an
svg
into the page, it seems to me like it would be more generic to give graphics crates aNode
or something, and then let them create and insert an inner element?Or maybe there's something I'm missing here?
The text was updated successfully, but these errors were encountered: