From 321610cdfc82f196d42c17635381fe4617c59d1a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Daniel=20Calvi=C3=B1o=20S=C3=A1nchez?= Date: Thu, 4 May 2023 19:29:44 +0200 Subject: [PATCH] Allow "wasm-unsafe-eval" in CSP MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Daniel Calviño Sánchez --- .../app_upgrade_guide/upgrade_to_28.rst | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/developer_manual/app_publishing_maintenance/app_upgrade_guide/upgrade_to_28.rst b/developer_manual/app_publishing_maintenance/app_upgrade_guide/upgrade_to_28.rst index 1cccc906f3a..8d3719341ff 100644 --- a/developer_manual/app_publishing_maintenance/app_upgrade_guide/upgrade_to_28.rst +++ b/developer_manual/app_publishing_maintenance/app_upgrade_guide/upgrade_to_28.rst @@ -41,6 +41,11 @@ Added APIs * ``files:node:moved``: the node has been moved (and its data is already updated) * ``files:node:updated``: the node data has been updated +* ``\OCP\AppFramework\Http\EmptyContentSecurityPolicy::allowEvalWasm(bool)``: sets ``wasm-unsafe-eval`` in ``script-src`` of the Content Security Policy `to allow compilation and execution of WebAssembly on the page `_ + + * ``wasm-unsafe-eval`` is `supported by most browsers `_ + * WebAssembly compilation and execution in worker threads is not affected by this directive (browsers allow compilation and execution of WebAssembly in worker threads by default) + Changed APIs ^^^^^^^^^^^^