Update sample json.

GoogleChrome · Dec 18, 2024 · 5d86c36 · 5d86c36
1 parent 268229b
commit 5d86c36
Show file tree

Hide file tree

Showing 4 changed files with 5 additions and 5 deletions.
diff --git a/core/test/fixtures/user-flows/reports/sample-flow-result.json b/core/test/fixtures/user-flows/reports/sample-flow-result.json
@@ -2197,7 +2197,7 @@
           "clickjacking-mitigation": {
             "id": "clickjacking-mitigation",
             "title": "Ensure Clickjacking mitigation through XFO or CSP.",
-            "description": "Deployment of either the X-Frame-Options or Content-Security-Policy (with the frame-ancestors directive) header will prevent Clickjacking attacks. While the XFO header is simpler to deploy, the CSP header is more flexible. [Learn more about Clickjacking prevention](https://developer.mozilla.org/en-US/docs/Web/Security/Practical_implementation_guides/Clickjacking).",
+            "description": "Deployment of either the X-Frame-Options or Content-Security-Policy (with the frame-ancestors directive) header will prevent Clickjacking attacks. While the XFO header is simpler to deploy, the CSP header is more flexible. [Learn more about mitigating Clickjacking with XFO and CSP](https://developer.chrome.com/docs/lighthouse/best-practices/clickjacking-mitigation).",
             "score": 1,
             "scoreDisplayMode": "informative",
             "details": {
@@ -20125,7 +20125,7 @@
           "clickjacking-mitigation": {
             "id": "clickjacking-mitigation",
             "title": "Ensure Clickjacking mitigation through XFO or CSP.",
-            "description": "Deployment of either the X-Frame-Options or Content-Security-Policy (with the frame-ancestors directive) header will prevent Clickjacking attacks. While the XFO header is simpler to deploy, the CSP header is more flexible. [Learn more about Clickjacking prevention](https://developer.mozilla.org/en-US/docs/Web/Security/Practical_implementation_guides/Clickjacking).",
+            "description": "Deployment of either the X-Frame-Options or Content-Security-Policy (with the frame-ancestors directive) header will prevent Clickjacking attacks. While the XFO header is simpler to deploy, the CSP header is more flexible. [Learn more about mitigating Clickjacking with XFO and CSP](https://developer.chrome.com/docs/lighthouse/best-practices/clickjacking-mitigation).",
             "score": 1,
             "scoreDisplayMode": "informative",
             "details": {

diff --git a/core/test/results/sample_v2.json b/core/test/results/sample_v2.json
@@ -2852,7 +2852,7 @@
     "clickjacking-mitigation": {
       "id": "clickjacking-mitigation",
       "title": "Ensure Clickjacking mitigation through XFO or CSP.",
-      "description": "Deployment of either the X-Frame-Options or Content-Security-Policy (with the frame-ancestors directive) header will prevent Clickjacking attacks. While the XFO header is simpler to deploy, the CSP header is more flexible. [Learn more about Clickjacking prevention](https://developer.mozilla.org/en-US/docs/Web/Security/Practical_implementation_guides/Clickjacking).",
+      "description": "Deployment of either the X-Frame-Options or Content-Security-Policy (with the frame-ancestors directive) header will prevent Clickjacking attacks. While the XFO header is simpler to deploy, the CSP header is more flexible. [Learn more about mitigating Clickjacking with XFO and CSP](https://developer.chrome.com/docs/lighthouse/best-practices/clickjacking-mitigation).",
       "score": 1,
       "scoreDisplayMode": "informative",
       "details": {

diff --git a/shared/localization/locales/en-US.json b/shared/localization/locales/en-US.json
diff --git a/shared/localization/locales/en-XL.json b/shared/localization/locales/en-XL.json