Skip to content

Expanding security and privacy considerations #1

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

Open
lknik wants to merge 1 commit into
base: gh-pages
Choose a base branch
from
Open

Expanding security and privacy considerations #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
10 changes: 5 additions & 5 deletions releases/PR.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -738,16 +738,16 @@ <h2 id="w3c-proposed-recommendation-29-march-2016"><abbr title="World Wide Web C
</span></h2><p><em>This section is non-normative.</em></p>
<p>
The API defined in this specification is used to determine the battery
status of the hosting device.
status of the hosting device. The information provided by Battery API may possibly be used in profiling the
user via analysis of device use patterns and potentially to track users on the Web.

</p>
<p>
The user agent <em class="rfc2119" title="SHOULD">SHOULD</em> not expose high precision readouts of battery
status information as that can introduce a new fingerprinting vector.
</p>
<p>
The user agent <em class="rfc2119" title="MAY">MAY</em> ask the user for battery status information access,
or alternatively, enforce the user permission requirement in its
private browsing modes.
The user agent <em class="rfc2119" title="SHOULD">SHOULD</em> be subject to permissions.
</p>
<p>
The user agent <em class="rfc2119" title="SHOULD">SHOULD</em> inform the user of the API use by scripts in an
Expand Down Expand Up @@ -1077,4 +1077,4 @@ <h3 id="h-event-handlers" resource="#h-event-handlers"><span property="xhv:role"
</dd><dt id="bib-HTML5">[HTML5]</dt><dd>Ian Hickson; Robin Berjon; Steve Faulkner; Travis Leithead; Erika Doyle Navara; Edward O'Connor; Silvia Pfeiffer. W3C. <a href="http://www.w3.org/TR/html5/" property="dc:requires"><cite>HTML5</cite></a>. 28 October 2014. W3C Recommendation. URL: <a href="http://www.w3.org/TR/html5/" property="dc:requires">http://www.w3.org/TR/html5/</a>
</dd><dt id="bib-RFC2119">[RFC2119]</dt><dd>S. Bradner. IETF. <a href="https://tools.ietf.org/html/rfc2119" property="dc:requires"><cite>Key words for use in RFCs to Indicate Requirement Levels</cite></a>. March 1997. Best Current Practice. URL: <a href="https://tools.ietf.org/html/rfc2119" property="dc:requires">https://tools.ietf.org/html/rfc2119</a>
</dd><dt id="bib-WEBIDL">[WEBIDL]</dt><dd>Cameron McCormack; Boris Zbarsky. W3C. <a href="http://www.w3.org/TR/WebIDL-1/" property="dc:requires"><cite>WebIDL Level 1</cite></a>. 8 March 2016. W3C Candidate Recommendation. URL: <a href="http://www.w3.org/TR/WebIDL-1/" property="dc:requires">http://www.w3.org/TR/WebIDL-1/</a>
</dd></dl></section></section><p role="navigation" id="back-to-top"><a href="#toc"><abbr title="Back to Top">↑</abbr></a></p><script async="" defer="" src="https://www.w3.org/scripts/TR/2016/fixup.js"></script></body></html>
</dd></dl></section></section><p role="navigation" id="back-to-top"><a href="#toc"><abbr title="Back to Top">↑</abbr></a></p><script async="" defer="" src="https://www.w3.org/scripts/TR/2016/fixup.js"></script></body></html>