Skip to content

Commit

Permalink
Tie [=latest reading=] map to an origin
Browse files Browse the repository at this point in the history
In order to prevent unsanctioned cross-origin communication.
  • Loading branch information
Mikhail Pozdnyakov committed Sep 15, 2017
1 parent eda5fa0 commit e7fec3b
Show file tree
Hide file tree
Showing 2 changed files with 209 additions and 208 deletions.
14 changes: 8 additions & 6 deletions index.bs
Original file line number Diff line number Diff line change
Expand Up @@ -751,14 +751,16 @@ A <dfn id=concept-sensor>sensor</dfn> has an associated [=ordered set|set=]
of <dfn>activated sensor objects</dfn>.
This set is initially [=set/is empty|empty=].

A [=sensor=] has an associated <dfn>latest reading</dfn> [=ordered map|map=]
which holds the latest available [=sensor readings=].
For the current [=browsing context=] a [=sensor=] has an associated <dfn>latest reading</dfn>
[=ordered map|map=] which holds the latest available [=sensor readings=].

Any time the UA obtains a new [=sensor reading=] for a [=sensor=] from the underlying platform,
it invokes [=update latest reading=] with the [=sensor=] and the [=sensor reading=] as arguments.
Note: User agents may share [=sensor readings=] [=ordered map|map=] between different
[=browsing context|contexts=] only if the [=origins=] of these contexts' [=active documents=]
are [=same origin-domain=].

Issue: does the [=latest reading=] map need to be
tied to an origin?
Any time the user agent obtains a new [=sensor reading=] for a [=sensor=] from the underlying
platform, it invokes [=update latest reading=] with the [=sensor=] and the [=sensor reading=]
as arguments.

The [=latest reading=] [=ordered map|map=]
contains an [=map/entry=]
Expand Down
Loading

0 comments on commit e7fec3b

Please sign in to comment.