Skip to content
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.

Sign up for GitHub

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

Rewrite privacy considerations section #215

Merged
merged 21 commits into from
Oct 25, 2022
Merged

Rewrite privacy considerations section #215

Changes from 4 commits
Commits
Show all changes
21 commits
Select commit Hold shift + click to select a range
a057762
Rewrite privacy considerations
marcoscaceres Oct 12, 2022
c05f547
Make into list, add event handling and lying
marcoscaceres Oct 12, 2022
2ee82e0
Merge branch 'gh-pages' into privacy
marcoscaceres Oct 12, 2022
4dd11d4
Update index.html
marcoscaceres Oct 12, 2022
625eb62
Update index.html
marcoscaceres Oct 12, 2022
0d6a585
Review feedback
marcoscaceres Oct 12, 2022
fed4f26
Update index.html
marcoscaceres Oct 13, 2022
a02add3
Review feedback
marcoscaceres Oct 13, 2022
9876fd2
Update index.html
marcoscaceres Oct 14, 2022
b36ca24
Rewrite based on feedback
marcoscaceres Oct 14, 2022
848ec4d
Merge branch 'gh-pages' into privacy
marcoscaceres Oct 14, 2022
5579b07
Merge branch 'gh-pages' into privacy
marcoscaceres Oct 16, 2022
64ee33c
Merge branch 'gh-pages' into privacy
marcoscaceres Oct 18, 2022
b06fc0f
Update based on feedback
marcoscaceres Oct 24, 2022
2a2b2ec
Merge branch 'gh-pages' into privacy
marcoscaceres Oct 24, 2022
c6e3d92
Merge branch 'gh-pages' into privacy
marcoscaceres Oct 24, 2022
562822d
Add [[initialType]] slot
marcoscaceres Oct 24, 2022
56642c0
reword
marcoscaceres Oct 24, 2022
eb30da6
reword
marcoscaceres Oct 24, 2022
783fc22
Update index.html
marcoscaceres Oct 24, 2022
afd3b18
Merge branch 'gh-pages' into privacy
marcoscaceres Oct 25, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 20 additions & 11 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -937,20 +937,29 @@ <h2>
</p>
</section>
</section>
<section class="informative">
<section>
<h2>
Privacy and Security Considerations
</h2>
<section>
<h3>
Access to aspects of a user's local computing environment
</h3>
<p>
The screen orientation type and angle of the device can be accessed
with the API specified in this document, and can be a potential
fingerprinting vector.
</p>
</section>
<p>
A screen's [=current orientation type|type=] and [=current orientation
angle|angle=] is a potential fingerprinting vector. To resist
marcoscaceres marked this conversation as resolved.
Show resolved Hide resolved
marcoscaceres marked this conversation as resolved.
Show resolved Hide resolved
fingerprinting (e.g., in private browsing), user agents MAY:
</p>
<ol>
<li>Restrict the value return by the {{ScreenOrientation/type}}
attribute to {{OrientationType/"portrait-primary"}} or
{{OrientationType/"landscape-secondary"}} so to match the screen's
aspect ratio.
</li>
marcoscaceres marked this conversation as resolved.
Show resolved Hide resolved
<li>Always return `0` for the value of the {{ScreenOrientation/angle}}
attribute
marcoscaceres marked this conversation as resolved.
Show resolved Hide resolved
</li>
marcoscaceres marked this conversation as resolved.
Show resolved Hide resolved
<li>If the screen orientation changes, not fire the
{{ScreenOrientation/onchange}} event to reveal a change to a
[=secondary=] orientation.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wouldn't this encourage battery-expensive polling instead? If you support rotating in a way that changes width/height of the viewport I think we should require that something changes. But limiting it two values for type and angle each seems reasonable.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wouldn't this encourage battery-expensive polling instead?

Sorry, I might need to word this better. The answer is "no", because the UA wouldn't fire events when switching from "X-primary" to "X-secondary". Only if "X" changes, would the event fire, but it would always report as "X-primary".

The reason the orientation change event does fire, is that the screen width/height would change, which is already observable either polling screen's attribute or simply by matchMedia("(orientation: landscape)").

</li>
</ol>
</section>
<section id="conformance"></section>
<section id="idl-index" class="appendix"></section>
Expand Down