Martin Robinson
Martin Robinson
A few other possibilities: - `script/dom/xml` - `script/dom/workers` - `script/dom/media`: Which could contain `audio` and `video`. - `script/dom/security`: Which would contain all CSP code. - `script/dom/canvas`: Which would contain `2d`,...
> I think canvas should be separated per types (webgpu and webgl already have own folders), so it's just a matter of adding canvas2d. I will do that. I think...
https://github.com/mozilla-firefox/firefox/tree/main/dom/canvas seems to contain WebGL related files. I think it would be nice to have a container for the generic canvas-related things that we have, otherwise they will be the...
> MDN names it "Canvas API": https://developer.mozilla.org/en-US/docs/Web/API/Canvas_API#reference and this refers to 2D only; webgl and webgpu have own sections. I would name it just canvas, but that's to vague IMO....
> Yeah, I know and I suggest we do it better then firefox and split more. I'm fine with a greater split, but I would like to see it like...
This means that canvas-related source files that do not relate the 2d rendering context will be in the root directory of the DOM bindings, which I think isn't a great...
> > This means that canvas-related source files that do not relate the 2d rendering context will be in the root directory of the DOM bindings, which I think isn't...
@sagudev Yes, that sound great to me!
Another good set of things here would be media including anything prefixed with `media`, `texttrack`, `videotrack`, and `vtt`.
Can you explain the benefits of using an external templating engine?