- From: Shivani Sharma <notifications@github.com>
- Date: Mon, 23 May 2022 09:53:15 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 23 May 2022 16:53:27 UTC
As @domfarolino mentioned, the sensors will all be disabled inside a fenced frame tree. Other APIs that could be side channels like Navigator.vibrate are also disabled inside a fenced frame tree ([code source link](https://chromium-review.googlesource.com/c/chromium/src/+/3473683)). Similarly programmatic focus is disabled as described [here](https://github.com/WICG/fenced-frame/blob/master/explainer/integration_with_web_platform.md#focus). The document also describes other APIs that are on our radar e.g intersection observer. Updated the documentation [here](https://github.com/WICG/fenced-frame/blob/master/explainer/permission_document_policies.md#summary) for describing interaction with Permissions API. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/735#issuecomment-1134916314 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/735/1134916314@github.com>
Received on Monday, 23 May 2022 16:53:27 UTC