Skip to content

Commit

Permalink
Ensure the automatic beacon data map is a reference (#141)
Browse files Browse the repository at this point in the history
  • Loading branch information
blu25 authored Mar 28, 2024
1 parent 5b3cdb6 commit fd26825
Showing 1 changed file with 7 additions and 0 deletions.
7 changes: 7 additions & 0 deletions spec.bs
Original file line number Diff line number Diff line change
Expand Up @@ -2554,6 +2554,8 @@ CORP violation report=] algorithm, as leaving it unfenced may cause a privacy le
<div algorithm>
To <dfn>get the automatic beacon data mapping to use</dfn> given a {{Document}} |sourceDocument|:

1. [=Assert=] these steps are running on |sourceDocument|'s [=event loop=].

1. Let |automatic beacon data map| be a new empty [=Document/automatic beacon data map=].

1. Let |current navigable| be |sourceDocument|'s [=node navigable=].
Expand All @@ -2573,6 +2575,11 @@ CORP violation report=] algorithm, as leaving it unfenced may cause a privacy le
1. Set |current navigable| to |current navigable|'s [=navigable/parent=].

1. Return |automatic beacon data map|.

Note: The returned map is meant to hold references to the original {{Document}}'s
[=Document/automatic beacon data map=]s that were used to build |automatic beacon data map|. These
are later modified in [=attempt to send an automatic beacon=] to clear out any beacon data with
[=automatic beacon data/once=] set to true.
</div>

<div algorithm=snapshot-source-snapshot-params>
Expand Down

0 comments on commit fd26825

Please sign in to comment.