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

Jump to bottom

Have deviceId follow partitioning rules for storage (such as localStorage) #674

Merged
merged 3 commits into from
Apr 2, 2020
Merged

Have deviceId follow partitioning rules for storage (such as localStorage) #674

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
bc990eb
Have deviceId follow partitioning rules for localStorage.
jan-ivar Apr 2, 2020
ed52891
Reword to reference nested browsing context.
jan-ivar Apr 2, 2020
49bbfb0
s/localStorage/storage (such as localStorage)/
jan-ivar Apr 2, 2020
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
11 changes: 9 additions & 2 deletions getusermedia.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3214,8 +3214,15 @@ <h2>Attributes</h2>
<p>The identifier of the represented device. The device MUST be
uniquely identified by its identifier and its <code><a
href="#def-mediadeviceinfo-kind">kind</a></code>.</p>
<p>The same identifier MUST be valid between browsing sessions of
this origin. The identifier SHOULD be origin-unique,
<p>To to ensure stored identifiers are recognized, the identifier
MUST be the same in documents of the same origin in <a data-cite=
"!HTML/#top-level-browsing-context">top-level browsing contexts.</a>
In iframes, whether or not the identifier is the same in documents
of the same origin or not, MUST follow the user agents'
partitioning rules for <a data-cite=
"!HTML/#dom-localstorage"><code>localStorage</code></a>, if any,
to not interfere with mitigations for cross-site correlation.
The identifier SHOULD be origin-unique,
in which case some sort of UUID is recommended.
If the identifier can uniquely identify the user, as is usually
the case with UUID, it MUST be un-guessable by browsing contexts
Expand Down