Skip to content

Add a Specific Restriction for "wasm-unsafe-eval" #203

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 14, 2025
Merged

Add a Specific Restriction for "wasm-unsafe-eval" #203

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions docs/05_Developing_Apps/content-security-policy-fe1a6db.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -603,6 +603,23 @@ Hyphenation

When native hyphenation is not available, a third-party library \(Hyphenopoly\) is used. This library uses WASM, which leads to CSP issues due to browser limitations. There is a fallback to `asm.js`, if WASM can't be used.

</td>
</tr>
<tr>
<td valign="top">

`sap.ndc.BarcodeScanner`

</td>
<td valign="top">

BarcodeScanner

</td>
<td valign="top">

`script-src` requires `wasm-unsafe-eval`

</td>
</tr>
<tr>
Expand Down
Loading