[Question] Firefox (and variants) users with WebAssembly disabled... #20223
-
|
I refuse to let websites use WebAssembly (I don't trust them and WA can be more tedious to reverse-engineer) but Ruffle seems to require it... any way for an extension (Ruffle in this case, with trusted SWFs) to bypass that and execute WebAssembly just for Ruffle? Maybe Firefox could provide WASM for extensions (optionally) in a separate control so users can keep pages disabled but extensions (including for embedded) can be enabled? (And in the case of Ruffle maybe a prompt to allow/disallow case by case/site?) |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 14 replies
-
|
I'm going to convert this to a discussion. The short answer is that I don't believe this is possible. The request for this feature should probably be made either on https://bugzilla.mozilla.org (ask the Mozilla team to add this as a separate about:config option) and/or on https://github.com/w3c/webextensions/issues (it may not be appropriate for the W3C though as they handle cross-browser implementations and many other browsers either make it hard to disable WebAssembly or don't have a way to do so at all). I think the only option is to enable it in about:config on the specific sites you want to use Ruffle on and disable it when not using them but as you know if those sites use WebAssembly themselves (unlikely but possible) they can execute it too. It is possible to enable Ruffle itself only on a per site basis using default MV3 features but it still needs WebAssembly enabled while you browse the site. Worth noting the reason it uses WebAssembly is it was written in Rust as that was the easiest way to make the cross-platform desktop app, which came first, and then one of the early developers cross-compiled it to WebAssembly to allow the extension to exist. |
Beta Was this translation helpful? Give feedback.
-
|
I'm a bit confused by the language regarding "Play Flash content in Ruffle" and "Play Flash content even on sites that disallow Ruffle" when it comes to "Autoplay Flash content (click to unmute)". If I wanted Ruffle to run on all sites but prompt me before running any actual flash content...is that possible? The "autoplay/unmute" wordings are a bit ambiguous for me. |
Beta Was this translation helpful? Give feedback.
-
|
So by default Ruffle shows an orange play button where Flash content appears on a site and won't start playing the content until you click it. Autoplay Flash Content (click to unmute) starts the content immediately (with no sound because audio autoplay is not supported in modern browsers) and hides the play button. This is as similar as we can get to Flash's own behavior, but may be undesirable. Play Flash content in Ruffle is basically the enable/disable toggle for the extension itself. Play Flash content even on sites that disallow Ruffle will mean Ruffle is used even on websites that add custom HTML code to their site that tells Ruffle not to play Flash content on it. |
Beta Was this translation helpful? Give feedback.
-
By the way, with #20255 I am making Ruffle use a standard content script, though it will execute in the MAIN ExecutionWorld (for now, in the future hopefully I can make some parts of it ISOLATED but that will need a larger change). So if you can convince Mozilla to add a separate config toggle for allowing only extensions to use WebAssembly, if they implement it by allowing extension content scripts in any ExecutionWorld to run WebAssembly (instead of just ISOLATED scripts), that would let Ruffle run. So the best place for that request is likely https://bugzilla.mozilla.org/. |
Beta Was this translation helpful? Give feedback.
-
|
I opened the bug myself: https://bugzilla.mozilla.org/show_bug.cgi?id=1962849 |
Beta Was this translation helpful? Give feedback.
-
Very much appreciated, I would have opened one but was banned long ago for disagreeing with the direction Mozilla has been taking. |
Beta Was this translation helpful? Give feedback.
I'm going to convert this to a discussion. The short answer is that I don't believe this is possible.
The request for this feature should probably be made either on https://bugzilla.mozilla.org (ask the Mozilla team to add this as a separate about:config option) and/or on https://github.com/w3c/webextensions/issues (it may not be appropriate for the W3C though as they handle cross-browser implementations and many other browsers either make it hard to disable WebAssembly or don't have a way to do so at all).
I think the only option is to enable it in about:config on the specific sites you want to use Ruffle on and disable it when not using them but as you know if those sites use WebAssembl…