Re: [w3ctag/design-reviews] Review request for Fenced Frames (Issue #735)

> 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.

Additionally, would like to point out that many of the side channels have been identified and are documented in the explainer but that may not be an exhaustive list and we look forward to continue adding to it and welcome feedback.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/735#issuecomment-1153800876
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/735/1153800876@github.com>