Skip to content

Commit

Permalink
chore: revert secure-context xref... still busted
Browse files Browse the repository at this point in the history
  • Loading branch information
Marcos Cáceres committed Feb 4, 2020
1 parent 792b09b commit 4b435c6
Showing 1 changed file with 5 additions and 4 deletions.
9 changes: 5 additions & 4 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -381,8 +381,8 @@ <h2>
<a>push subscription</a> to send <a>push messages</a> to another <a>push subscription</a>.
</p>
<p>
<a>User agents</a> MUST implement the Push API to only be available in <a data-cite=
"secure-contexts#secure-context">secure contexts</a>. This provides better protection for
<a>User agents</a> MUST implement the Push API to only be available in a <a data-cite=
"secure-contexts#secure-context">secure context</a>. This provides better protection for
the user against man-in-the-middle attacks intended to obtain push subscription data.
Browsers may ignore this rule for development purposes only.
</p>
Expand Down Expand Up @@ -549,8 +549,9 @@ <h2>
</li>
<li>Return |promise| and continue the following steps asynchronously.
</li>
<li>If the <a>current settings object</a> is not a <a>secure context</a>, reject |promise|
with a {{DOMException}} whose name is {{"SecurityError"}} and terminate these steps.
<li>If the <a>current settings object</a> is not a <a data-cite=
"secure-contexts#secure-context">secure context</a>, reject |promise| with a
{{DOMException}} whose name is {{"SecurityError"}} and terminate these steps.
</li>
<li>If the |options| argument includes a non-null value for the
{{PushSubscriptionOptions/applicationServerKey}} attribute, run the following sub-steps:
Expand Down

0 comments on commit 4b435c6

Please sign in to comment.