Tie [=latest reading=] map to an origin #267
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@lknik PTAL |
anssiko
requested changes
Sep 15, 2017
index.bs
Outdated
| @@ -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> | |||
There was a problem hiding this comment.
The current browsing context's sensor has
index.bs
Outdated
|
|
||
| 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 |
There was a problem hiding this comment.
s/may/can/
We don't generally use RFC 2119 terms in informative notes for clarity.
alexshalamov
approved these changes
Sep 15, 2017
|
lgtm with @anssiko nits |
In order to prevent unsanctioned cross-origin communication.
pozdnyakov
force-pushed
the
tie_latest_reading_to_origin
branch
from
e7fec3b
to
af9b5dc
Compare
|
@anssiko the patch is updated due to your comments |
|
Good to see that thing! |
|
@anssiko could you PTAL at the latest patch? |
|
LGTM. |
rakuco
added a commit
that referenced
this pull request
Feb 16, 2024
The original note was added in #267 and expanded in #347, but its advice is impractical: - Sharing the activated sensors objects between multiple browsing contexts/documents/windows means these Sensor objects could potentially be shared by contexts in different top-level traversables (i.e. different tabs). Furthermore, if "can expose sensor readings" passes for one context but not the other, "update sensor reading" would still invoke "report latest reading updated" with sensors that cannot expose sensor readings. - Similarly, if the latest reading map is shared between multiple contexts, an update would affect all contexts, including those for which "update sensor reading" should not have been invoked in the first place (e.g. two pages with the same origin share the latest readings map, but only one is visible; updates to the latest reading map would be accessible from the other as well). PR #267 also made the "platform sensor" concept used in this section per-browsing context (although in a very confusing way), which on its own is a stricter requirement than what the note allowed, so we can drop the note without making things less secure. Incidentally, this also gets rid of one of the usages of "browsing context" in the spec, which helps with #444.
rakuco
added a commit
that referenced
this pull request
Feb 17, 2024
The original note was added in #267 and expanded in #347, but its advice is impractical: - Sharing the activated sensors objects between multiple browsing contexts/documents/windows means these Sensor objects could potentially be shared by contexts in different top-level traversables (i.e. different tabs). Furthermore, if "can expose sensor readings" passes for one context but not the other, "update sensor reading" would still invoke "report latest reading updated" with sensors that cannot expose sensor readings. - Similarly, if the latest reading map is shared between multiple contexts, an update would affect all contexts, including those for which "update sensor reading" should not have been invoked in the first place (e.g. two pages with the same origin share the latest readings map, but only one is visible; updates to the latest reading map would be accessible from the other as well). PR #267 also made the "platform sensor" concept used in this section per-browsing context (although in a very confusing way), which on its own is a stricter requirement than what the note allowed, so we can drop the note without making things less secure. Incidentally, this also gets rid of one of the usages of "browsing context" in the spec, which helps with #444.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In order to prevent unsanctioned cross-origin communication.
Preview | Diff