I see the following in the console: ``` console.error: (new ReferenceError("WebAssembly is not defined", "resource://gre/actors/TranslationsParent.sys.mjs", 2710)) ``` Further I can find the construct `return WebAssembly.validate(` in the ml/content/Utils.sys.mjs. Better way will be adding of the following in detect Wasm feature functions (which is fixes the refresh button): ``` --- a/toolkit/components/translations/actors/TranslationsParent.sys.mjs +++ b/toolkit/components/translations/actors/TranslationsParent.sys.mjs @@ -2707,6 +2707,7 @@ export class TranslationsParent extends JSWindowActorParent { * Validate some simple Wasm that uses a SIMD operation. */ function detectSimdSupport() { + if (typeof WebAssembly == "undefined") { return false; } return WebAssembly.validate( new Uint8Array( // ``` ``` I don't know the reason why JavaScript exception in the translation code affects chrome's buttons.
Bug 1890137 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I see the following in the console: ``` console.error: (new ReferenceError("WebAssembly is not defined", "resource://gre/actors/TranslationsParent.sys.mjs", 2710)) ``` Further I can find the construct `return WebAssembly.validate(` in the ml/content/Utils.sys.mjs. Better way will be adding of the following in detect Wasm feature functions (which fixes the refresh button): ``` --- a/toolkit/components/translations/actors/TranslationsParent.sys.mjs +++ b/toolkit/components/translations/actors/TranslationsParent.sys.mjs @@ -2707,6 +2707,7 @@ export class TranslationsParent extends JSWindowActorParent { * Validate some simple Wasm that uses a SIMD operation. */ function detectSimdSupport() { + if (typeof WebAssembly == "undefined") { return false; } return WebAssembly.validate( new Uint8Array( // ``` ``` I don't know the reason why JavaScript exception in the translation code affects the chrome's buttons.