diff --git a/core/test/fixtures/user-flows/reports/sample-flow-result.json b/core/test/fixtures/user-flows/reports/sample-flow-result.json index 6381e9c57e7c..e2f6a1700e21 100644 --- 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 index cbcc77ad717e..3a651cc0388d 100644 --- 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 index 2623cc0a4919..59fec5aa84ff 100644 --- a/shared/localization/locales/en-US.json +++ b/shared/localization/locales/en-US.json @@ -768,7 +768,7 @@ "message": "Severity" }, "core/audits/clickjacking-mitigation.js | description": { - "message": "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)." + "message": "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)." }, "core/audits/clickjacking-mitigation.js | noClickjackingMitigation": { "message": "No Clickjacking mitigation found." diff --git a/shared/localization/locales/en-XL.json b/shared/localization/locales/en-XL.json index 2c05aa9413ed..ff44817113ae 100644 --- a/shared/localization/locales/en-XL.json +++ b/shared/localization/locales/en-XL.json @@ -768,7 +768,7 @@ "message": "Ŝév̂ér̂ít̂ý" }, "core/audits/clickjacking-mitigation.js | description": { - "message": "D̂ép̂ĺôým̂én̂t́ ôf́ êít̂h́êŕ t̂h́ê X́-F̂ŕâḿê-Óp̂t́îón̂ś ôŕ Ĉón̂t́êńt̂-Śêćûŕît́ŷ-Ṕôĺîćŷ (ẃît́ĥ t́ĥé f̂ŕâḿê-án̂ćêśt̂ór̂ś d̂ír̂éĉt́îv́ê) h́êád̂ér̂ ẃîĺl̂ ṕr̂év̂én̂t́ Ĉĺîćk̂j́âćk̂ín̂ǵ ât́t̂áĉḱŝ. Ẃĥíl̂é t̂h́ê X́F̂Ó ĥéâd́êŕ îś ŝím̂ṕl̂ér̂ t́ô d́êṕl̂óŷ, t́ĥé ĈŚP̂ h́êád̂ér̂ íŝ ḿôŕê f́l̂éx̂íb̂ĺê. [Ĺêár̂ń m̂ór̂é âb́ôút̂ Ćl̂íĉḱĵáĉḱîńĝ ṕr̂év̂én̂t́îón̂](https://developer.mozilla.org/en-US/docs/Web/Security/Practical_implementation_guides/Clickjacking)." + "message": "D̂ép̂ĺôým̂én̂t́ ôf́ êít̂h́êŕ t̂h́ê X́-F̂ŕâḿê-Óp̂t́îón̂ś ôŕ Ĉón̂t́êńt̂-Śêćûŕît́ŷ-Ṕôĺîćŷ (ẃît́ĥ t́ĥé f̂ŕâḿê-án̂ćêśt̂ór̂ś d̂ír̂éĉt́îv́ê) h́êád̂ér̂ ẃîĺl̂ ṕr̂év̂én̂t́ Ĉĺîćk̂j́âćk̂ín̂ǵ ât́t̂áĉḱŝ. Ẃĥíl̂é t̂h́ê X́F̂Ó ĥéâd́êŕ îś ŝím̂ṕl̂ér̂ t́ô d́êṕl̂óŷ, t́ĥé ĈŚP̂ h́êád̂ér̂ íŝ ḿôŕê f́l̂éx̂íb̂ĺê. [Ĺêár̂ń m̂ór̂é âb́ôút̂ ḿît́îǵât́îńĝ Ćl̂íĉḱĵáĉḱîńĝ ẃît́ĥ X́F̂Ó âńd̂ ĆŜṔ](https://developer.chrome.com/docs/lighthouse/best-practices/clickjacking-mitigation)." }, "core/audits/clickjacking-mitigation.js | noClickjackingMitigation": { "message": "N̂ó Ĉĺîćk̂j́âćk̂ín̂ǵ m̂ít̂íĝát̂íôń f̂óûńd̂."