summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/desktop-client-v1.md13
1 files changed, 12 insertions, 1 deletions
diff --git a/docs/desktop-client-v1.md b/docs/desktop-client-v1.md
index 23287dd..c0bbb90 100644
--- a/docs/desktop-client-v1.md
+++ b/docs/desktop-client-v1.md
@@ -181,7 +181,18 @@ Electron it is nearly all of it.
### 3.1 What running it changed
-Three of the statements above were wrong, and only launching the application found them.
+Four of the statements above were wrong, and only launching the application found them.
+
+**"Nothing here needs a camera, a microphone or a location" was true, and the handler
+written from it was still wrong.** Denying every permission also denied `fullscreen`, and
+Chromium's own video controls ask for it — so a film could not be watched full-screen.
+What makes this worth recording rather than just fixing: **a denied `fullscreen` does not
+reject.** `requestFullscreen()` returns a promise that never settles. No error, no console
+message, nothing in the renderer that names a permission; the button simply does nothing,
+and the operator reported it as "impossible to go full-screen" with no lead to follow. The
+probe reported `NEVER SETTLED` while the main process logged `PERMISSION ASKED:
+fullscreen`, which is what tied the two ends together. The handler now enumerates what is
+*granted* — one entry — so anything Chromium adds later still arrives refused.
**The CSP cannot live in a `<meta>` tag.** `frame-ancestors` is ignored there — Chromium
says so in the console — so a policy carrying it has one directive that silently does