Todd Tanner

Working fine for others when done correctly. #588

@abernier I just started using ffmpeg.wasm this week and I am also seeing the "aborted" message even when a command completes successfully which is not what I would expect.

I have my Blazor WASM V3 browser extension working on every page using the below declarativeNetRequest rule to remove CSP rules in page response headers. Not a perfect solution, but...

I'm sure it would be. Another method is to have the content page message the background script (extension service worker) when loading Blazor WASM fails due to CSP by listening...

I am using github.com to test fixes / workarounds for the WebAssembly.instantiateStreaming issue due to CSP violations in extension content mode. My Blazor extension is working on github.com with the...

The below is working in Chrome. I haven't tested Firefox yet. This patches CSP rules to include 'wasm-unsafe-eval' and reloads the tab to allow Blazor to load. in content script...

After finally getting my Blazor extension working in Firefox I am surprised to see that Firefox does not have the 'wasm-unsafe-eval' issue that Chrome has. Tested GitHub and it is...

dynamic imports in the service worker not being supported does make it a lot harder. It does not seem likely that they will enable it any time soon. > import()...

I made the requested changes. Not sure if I missed something. It says "Merging is blocked" "Merging can be performed automatically once the requested changes are addressed."

You can add your request here: [Proposed Encoders / Decoders Libraries](https://github.com/ffmpegwasm/ffmpeg.wasm/issues/61)