Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Specifies whether WebAssembly modules can be sent cross-origin (obsolete)
OBSOLETE: This policy is obsolete and doesn't work after Microsoft Edge version 98.
Supported versions
- On Windows and macOS since 95, until 98
Description
Specifies whether WebAssembly modules can be sent to another window or worker cross-origin. Cross-origin WebAssembly module sharing was deprecated as part of the efforts to deprecate document.___domain, see https://github.com/mikewest/deprecating-document-___domain. This policy allowed re-enabling of cross-origin WebAssembly module sharing. This policy is obsolete because it was intended to offer a longer transition period in the deprecation process.
If you enable this policy, sites can send WebAssembly modules cross-origin without restrictions.
If you disable or don't configure this policy, sites can only send WebAssembly modules to windows and workers in the same origin.
Supported features
- Can be mandatory: Yes
- Can be recommended: No
- Dynamic Policy Refresh: No - Requires browser restart
- Per Profile: Yes
- Applies to a profile that is signed in with a Microsoft account: Yes
Data type
- Boolean
Windows information and settings
Group Policy (ADMX) info
- GP unique name: CrossOriginWebAssemblyModuleSharingEnabled
- GP name: Specifies whether WebAssembly modules can be sent cross-origin (obsolete)
- GP path (Mandatory): Administrative Templates/Microsoft Edge
- GP path (Recommended): N/A
- GP ADMX file name: MSEdge.admx
Example value
Enabled
Registry settings
- Path (Mandatory): SOFTWARE\Policies\Microsoft\Edge
- Path (Recommended): N/A
- Value name: CrossOriginWebAssemblyModuleSharingEnabled
- Value type: REG_DWORD
Example registry value
0x00000001
Mac information and settings
- Preference Key name: CrossOriginWebAssemblyModuleSharingEnabled
- Example value:
<true/>