-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add the security-privacy-self-assessment for Origin Trial #110
Conversation
security-privacy-self-assessment.md
Outdated
|
||
### 2.1. What information might this feature expose to Web sites or other parties, and for what purposes is that exposure necessary? | ||
|
||
This API exposes the posture of the device, a physical state of a device. The posture typically apply only to device with a foldable screen or dual screens devices (devices with two screens connected with a physical hinge). The posture is typically derived from the hinge angle sensor but also few other sensors (for example if the keyboard is detached or not). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but can include data from other sensors as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you mean?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Typically the OS will take many inputs : hinge angle, keyboard docking state, kick stand state, window position etc etc and determine the posture. None of the decision making is done in the spec, certainly not exposed. As a matter of fact we should remove https://www.w3.org/TR/device-posture/#foldables and replace that with a section that explains how the posture could be derived, more like a FYI.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On Android for example https://www.w3.org/TR/device-posture/#foldables isn't true if the browser window is running on an external screen (the OS tells us continuous), despite the device being physically folded. Also on Android if you do a side by side app window (like say the browser and another app) the OS will tell us "continuous" because really there isn't much value in trying to layout stuff in half the screen.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you say, it is typically derived from the hinge angle sense, but then you also say a few other sensors... so is it always derived from all of these?
The posture is typically derived from the hinge angle sensor, but additional data can be used to determine the posture such as whether the keyboard is attached or not.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On Android it's hinge angle + window state. On Windows, it's Hinge Angle + other sensors.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But I don't think we should enter the specifics of each OS so let's keep generic. I think actually saying the posture is computed using a set of sensors sounds better.
d2ad71d
to
565e0e9
Compare
565e0e9
to
f38e30e
Compare
No description provided.