Re:Chrome intends to remove XSLT from the HTML spec
by codedokode on Tuesday August 19, 2025 @12:21PM
(#44953308)
What WebAudio needs to provide is only means to get or push buffers from/to audio devices and run code in high priority thread. There is no need for browser to provide implementation of low-pass filters, audio proccessing graphs and similar primitives.
Re:Chrome intends to remove XSLT from the HTML spec
by bigstrat2003 on Tuesday August 19, 2025 @12:39PM
(#44953488)
Honestly, even WASM makes it not very minimal in my book. A minimal browser should be HTML and perhaps a subset of CSS, that's it.
And no WebAudio and Canvas couldn't be implemented in client WASM without big security implication. If by module you mean inside the browser, them, what is the point of WASM here ?