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

Remove the incorrect paragraph about request() and revoke() having been removed from the spec. #79

Merged
merged 1 commit into from
Apr 15, 2016
Merged

Remove the incorrect paragraph about request() and revoke() having been removed from the spec. #79

Show file tree
Hide file tree
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
7 changes: 0 additions & 7 deletions index.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,13 +85,6 @@ spec: webidl
this document, please contact the editors or file an issue. We would
love to hear about it.
</p>
<p>
The initial intent of this document was to allow web applications to
request and revoke permissions explicitly in addition to querying the
permission status. This is an aspect of the specification that was
controversial thus removed from the current document in a spirit of
incremental changes: settling on a small API that can be improved.
</p>
</section>
<section class='non-normative'>
<h2 id="privacy-considerations">
Expand Down
7 changes: 1 addition & 6 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1345,7 +1345,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">The Permissions API</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-04-11">11 April 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-04-14">14 April 2016</time></span></h2>
<div data-fill-with="spec-metadata">
<dl>
<dt>This version:
Expand Down Expand Up @@ -1467,11 +1467,6 @@ <h2 class="heading settled" data-level="1" id="scope-of-this-document"><span cla
that has a permission model that wouldn’t fit in the model described in
this document, please contact the editors or file an issue. We would
love to hear about it. </p>
<p> The initial intent of this document was to allow web applications to
request and revoke permissions explicitly in addition to querying the
permission status. This is an aspect of the specification that was
controversial thus removed from the current document in a spirit of
incremental changes: settling on a small API that can be improved. </p>
</section>
<section class="non-normative">
<h2 class="heading settled" data-level="2" id="privacy-considerations"><span class="secno">2. </span><span class="content"> Privacy considerations </span><a class="self-link" href="#privacy-considerations"></a></h2>
Expand Down