From d449e5f0c378ca9035a33882f73f743371d7eba1 Mon Sep 17 00:00:00 2001
From: kkapsner <github@mail.kkapsner.de>
Date: Thu, 27 Feb 2020 17:30:58 +0100
Subject: [PATCH] Added FAQ for reCAPTCHA

For #398
---
 .documentation/faq/reCAPTCHA.md | 5 +++++
 1 file changed, 5 insertions(+)
 create mode 100644 .documentation/faq/reCAPTCHA.md

diff --git a/.documentation/faq/reCAPTCHA.md b/.documentation/faq/reCAPTCHA.md
new file mode 100644
index 0000000..1fc2379
--- /dev/null
+++ b/.documentation/faq/reCAPTCHA.md
@@ -0,0 +1,5 @@
+reCAPTCHA is not working!
+-----
+It's a known fact that the window API protection breaks reCAPTCHAs. The use the window.name API to store information about the captcha. The protection is designed to mitigate exactly such techniques of passing information from one domain to another. But in this case the information is shared with an embedded HTML page (an <iframe> tag). As the information gets lost when the top level page navigates somewhere the tracking potential is quite limited in such a scenario.
+
+So in conclusion you can enable "Allow window.name in frames" to make reCAPTCHA work and still don't have to worry to much about tracking with window.name.
\ No newline at end of file