Skip to content

Commit

Permalink
blacklist -> blocklist, resolves #96
Browse files Browse the repository at this point in the history
  • Loading branch information
inexorabletash committed Oct 4, 2016
1 parent 44d82bf commit 0173fc0
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 7 deletions.
6 changes: 3 additions & 3 deletions index.bs
Expand Up @@ -5845,17 +5845,17 @@ from third-party origins that caused data to be stored.
If this information is then used to present the view of data
currently in persistent storage, it would allow the user to make
informed decisions about which parts of the persistent storage to
prune. Combined with a blacklist ("delete this data and prevent
prune. Combined with a blocklist ("delete this data and prevent
this domain from ever storing data again"), the user can restrict
the use of persistent storage to sites that she trusts.

</dd>

<dt>Shared blacklists</dt>
<dt>Shared blocklists</dt>
<dd>

User agents may allow users to share their persistent storage
domain blacklists.
domain blocklists.

This would allow communities to act together to protect their
privacy.
Expand Down
8 changes: 4 additions & 4 deletions index.html
Expand Up @@ -1427,7 +1427,7 @@
<div class="head">
<p data-fill-with="logo"><a class="logo" href="http://www.w3.org/"> <img alt="W3C" height="48" src="https://www.w3.org/StyleSheets/TR/2016/logos/W3C" width="72"> </a> </p>
<h1 class="p-name no-ref" id="title">Indexed Database API 2.0</h1>
<h2 class="no-num no-toc no-ref heading settled" id="subtitle"><span class="content">Editor’s Draft, <time class="dt-updated" datetime="2016-09-29">29 September 2016</time></span></h2>
<h2 class="no-num no-toc no-ref heading settled" id="subtitle"><span class="content">Editor’s Draft, <time class="dt-updated" datetime="2016-10-04">4 October 2016</time></span></h2>
<div data-fill-with="spec-metadata">
<dl>
<dt>This version:
Expand Down Expand Up @@ -5787,13 +5787,13 @@ <h3 class="heading settled" data-level="8.1" id="user-tracking"><span class="sec
<p>If this information is then used to present the view of data
currently in persistent storage, it would allow the user to make
informed decisions about which parts of the persistent storage to
prune. Combined with a blacklist ("delete this data and prevent
prune. Combined with a blocklist ("delete this data and prevent
this domain from ever storing data again"), the user can restrict
the use of persistent storage to sites that she trusts.</p>
<dt>Shared blacklists
<dt>Shared blocklists
<dd>
<p>User agents may allow users to share their persistent storage
domain blacklists.</p>
domain blocklists.</p>
<p>This would allow communities to act together to protect their
privacy.</p>
</dl>
Expand Down

0 comments on commit 0173fc0

Please sign in to comment.