From 46c73d09152800276a92e9ae2885b4c7249fbd62 Mon Sep 17 00:00:00 2001
From: Alex Xiong <a.xiong@sap.com>
Date: Mon, 13 Oct 2025 14:05:39 +0800
Subject: [PATCH] Add a Specific Restriction for "wasm-unsafe-eval"

---
 .../content-security-policy-fe1a6db.md          | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/docs/05_Developing_Apps/content-security-policy-fe1a6db.md b/docs/05_Developing_Apps/content-security-policy-fe1a6db.md
index 65057095..832fe27b 100644
--- a/docs/05_Developing_Apps/content-security-policy-fe1a6db.md
+++ b/docs/05_Developing_Apps/content-security-policy-fe1a6db.md
@@ -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>