[Foldable] CSS - TAG Security and Privacy questionnaire

[dlibby-]

This has been created by cut-and-paste from https://w3ctag.github.io/security-questionnaire/, as requested in the TAG review instructions.

1. What information might this feature expose to Web sites or other parties, and for what purposes is that exposure necessary? This feature exposes information about a foldable device, when a window is spanning across a fold. For some devices, this information may already be available via the window.screen* properties. This exposure is necessary for web developers to be able to adaptively position content away from the fold/hinge.

2. Is this specification exposing the minimum amount of information necessary to power the feature? Yes, it is only exposing the geometry of the fold.

3. How does this specification deal with personal information or personally-identifiable information or information derived thereof? No personal information is exposed via this feature.

4. How does this specification deal with sensitive information? N/A

5. Does this specification introduce new state for an origin that persists across browsing sessions? No.

6. What information from the underlying platform, e.g. configuration data, is exposed by this specification to an origin? The geometry of a device that has a fold or hinge.

7. Does this specification allow an origin access to sensors on a user’s device? No.

8. What data does this specification expose to an origin? Please also document what data is identical to data exposed by other features, in the same or different contexts. The presence of a fold is indeed a bit of entropy in identifying individuals. However, as noted above, this information can in many cases be derived from existing information from the window.screen properties.

9. Does this specification enable new script execution/loading mechanisms? No.

10. Does this specification allow an origin to access other devices? No.

11. Does this specification allow an origin some measure of control over a user agent’s native UI? No.

12. What temporary identifiers might this specification create or expose to the web? No identifiers are created or exposed.

13. How does this specification distinguish between behavior in first-party and third-party contexts? This feature does not distinguish between these contexts.

14. How does this specification work in the context of a user agent’s Private Browsing or "incognito" mode? This feature does not distinguish between these modes.

15. Does this specification have a "Security Considerations" and "Privacy Considerations" section? Yes.

16. Does this specification allow downgrading default security characteristics? No.