-
Notifications
You must be signed in to change notification settings - Fork 18
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.
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
Update spec.bs to Change From Per-Origin to Per-Site Budgets #118
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
We update the spec to reflect the explainer changes landed in PR #112 . We are now going to use per-site privacy budgets instead of per-origin privacy budgets. This will better align with enrollment enforcement, which is also per-site.
xyaoinum
approved these changes
Sep 26, 2023
chromium-wpt-export-bot
pushed a commit
to web-platform-tests/wpt
that referenced
this pull request
Sep 28, 2023
We update to using per-site privacy budgets instead of per-origin privacy budgets. This will align with enrollment enforcement, which is per-site. See also WICG/shared-storage#112 and WICG/shared-storage#118. To accomplish this, we migrate the `SharedStorageDatabase` to version 4, where the `budget_mapping` table's `context_origin` column has been renamed to `context_site`, and any existing data for version 3 databases will have each serialized origin in that column replaced by the corresponding serialization of the origin's site. We also update the names and types of other members and parameters as needed. Bug: 1218540,1485598 Change-Id: I3d956f5f2cd54a5da76a20e7d63411b3b7fc51ef
jyasskin
approved these changes
Sep 28, 2023
chromium-wpt-export-bot
pushed a commit
to web-platform-tests/wpt
that referenced
this pull request
Sep 29, 2023
We update to using per-site privacy budgets instead of per-origin privacy budgets. This will align with enrollment enforcement, which is per-site. See also WICG/shared-storage#112 and WICG/shared-storage#118. To accomplish this, we migrate the `SharedStorageDatabase` to version 4, where the `budget_mapping` table's `context_origin` column has been renamed to `context_site`, and any existing data for version 3 databases will have each serialized origin in that column replaced by the corresponding serialization of the origin's site. We also update the names and types of other members and parameters as needed. Bug: 1218540,1485598 Change-Id: I3d956f5f2cd54a5da76a20e7d63411b3b7fc51ef
chromium-wpt-export-bot
pushed a commit
to web-platform-tests/wpt
that referenced
this pull request
Sep 29, 2023
We update to using per-site privacy budgets instead of per-origin privacy budgets. This will align with enrollment enforcement, which is per-site. See also WICG/shared-storage#112 and WICG/shared-storage#118. To accomplish this, we migrate the `SharedStorageDatabase` to version 4, where the `budget_mapping` table's `context_origin` column has been renamed to `context_site`, and any existing data for version 3 databases will have each serialized origin in that column replaced by the corresponding serialization of the origin's site. We also update the names and types of other members and parameters as needed. Bug: 1218540,1485598 Change-Id: I3d956f5f2cd54a5da76a20e7d63411b3b7fc51ef
chromium-wpt-export-bot
pushed a commit
to web-platform-tests/wpt
that referenced
this pull request
Oct 2, 2023
We update to using per-site privacy budgets instead of per-origin privacy budgets. This will align with enrollment enforcement, which is per-site. See also WICG/shared-storage#112 and WICG/shared-storage#118. To accomplish this, we migrate the `SharedStorageDatabase` to version 4, where the `budget_mapping` table's `context_origin` column has been renamed to `context_site`, and any existing data for version 3 databases will have each serialized origin in that column replaced by the corresponding serialization of the origin's site. We also update the names and types of other members and parameters as needed. Bug: 1218540,1485598 Change-Id: I3d956f5f2cd54a5da76a20e7d63411b3b7fc51ef
chromium-wpt-export-bot
pushed a commit
to web-platform-tests/wpt
that referenced
this pull request
Oct 2, 2023
We update to using per-site privacy budgets instead of per-origin privacy budgets. This will align with enrollment enforcement, which is per-site. See also WICG/shared-storage#112 and WICG/shared-storage#118. To accomplish this, we migrate the `SharedStorageDatabase` to version 4, where the `budget_mapping` table's `context_origin` column has been renamed to `context_site`, and any existing data for version 3 databases will have each serialized origin in that column replaced by the corresponding serialization of the origin's site. We also update the names and types of other members and parameters as needed. Bug: 1218540,1485598 Change-Id: I3d956f5f2cd54a5da76a20e7d63411b3b7fc51ef
aarongable
pushed a commit
to chromium/chromium
that referenced
this pull request
Oct 2, 2023
We update to using per-site privacy budgets instead of per-origin privacy budgets. This will align with enrollment enforcement, which is per-site. See also WICG/shared-storage#112 and WICG/shared-storage#118. To accomplish this, we migrate the `SharedStorageDatabase` to version 4, where the `budget_mapping` table's `context_origin` column has been renamed to `context_site`, and any existing data for version 3 databases will have each serialized origin in that column replaced by the corresponding serialization of the origin's site. We also update the names and types of other members and parameters as needed. Bug: 1218540,1485598 Change-Id: I3d956f5f2cd54a5da76a20e7d63411b3b7fc51ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4879582 Reviewed-by: Philip Rogers <pdr@chromium.org> Commit-Queue: Cammie Smith Barnes <cammie@chromium.org> Reviewed-by: Ayu Ishii <ayui@chromium.org> Reviewed-by: Garrett Tanzer <gtanzer@chromium.org> Reviewed-by: Avi Drissman <avi@chromium.org> Reviewed-by: danakj <danakj@chromium.org> Reviewed-by: Yao Xiao <yaoxia@chromium.org> Cr-Commit-Position: refs/heads/main@{#1204170}
chromium-wpt-export-bot
pushed a commit
to web-platform-tests/wpt
that referenced
this pull request
Oct 2, 2023
We update to using per-site privacy budgets instead of per-origin privacy budgets. This will align with enrollment enforcement, which is per-site. See also WICG/shared-storage#112 and WICG/shared-storage#118. To accomplish this, we migrate the `SharedStorageDatabase` to version 4, where the `budget_mapping` table's `context_origin` column has been renamed to `context_site`, and any existing data for version 3 databases will have each serialized origin in that column replaced by the corresponding serialization of the origin's site. We also update the names and types of other members and parameters as needed. Bug: 1218540,1485598 Change-Id: I3d956f5f2cd54a5da76a20e7d63411b3b7fc51ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4879582 Reviewed-by: Philip Rogers <pdr@chromium.org> Commit-Queue: Cammie Smith Barnes <cammie@chromium.org> Reviewed-by: Ayu Ishii <ayui@chromium.org> Reviewed-by: Garrett Tanzer <gtanzer@chromium.org> Reviewed-by: Avi Drissman <avi@chromium.org> Reviewed-by: danakj <danakj@chromium.org> Reviewed-by: Yao Xiao <yaoxia@chromium.org> Cr-Commit-Position: refs/heads/main@{#1204170}
chromium-wpt-export-bot
pushed a commit
to web-platform-tests/wpt
that referenced
this pull request
Oct 2, 2023
We update to using per-site privacy budgets instead of per-origin privacy budgets. This will align with enrollment enforcement, which is per-site. See also WICG/shared-storage#112 and WICG/shared-storage#118. To accomplish this, we migrate the `SharedStorageDatabase` to version 4, where the `budget_mapping` table's `context_origin` column has been renamed to `context_site`, and any existing data for version 3 databases will have each serialized origin in that column replaced by the corresponding serialization of the origin's site. We also update the names and types of other members and parameters as needed. Bug: 1218540,1485598 Change-Id: I3d956f5f2cd54a5da76a20e7d63411b3b7fc51ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4879582 Reviewed-by: Philip Rogers <pdr@chromium.org> Commit-Queue: Cammie Smith Barnes <cammie@chromium.org> Reviewed-by: Ayu Ishii <ayui@chromium.org> Reviewed-by: Garrett Tanzer <gtanzer@chromium.org> Reviewed-by: Avi Drissman <avi@chromium.org> Reviewed-by: danakj <danakj@chromium.org> Reviewed-by: Yao Xiao <yaoxia@chromium.org> Cr-Commit-Position: refs/heads/main@{#1204170}
Remove assumption that site is not opaque
github-actions bot
added a commit
that referenced
this pull request
Oct 3, 2023
SHA: edd815c Reason: push, by pythagoraskitty Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
moz-v2v-gh
pushed a commit
to mozilla/gecko-dev
that referenced
this pull request
Oct 6, 2023
…o per-site budgets, a=testonly Automatic update from web-platform-tests Shared Storage: Change from per-origin to per-site budgets We update to using per-site privacy budgets instead of per-origin privacy budgets. This will align with enrollment enforcement, which is per-site. See also WICG/shared-storage#112 and WICG/shared-storage#118. To accomplish this, we migrate the `SharedStorageDatabase` to version 4, where the `budget_mapping` table's `context_origin` column has been renamed to `context_site`, and any existing data for version 3 databases will have each serialized origin in that column replaced by the corresponding serialization of the origin's site. We also update the names and types of other members and parameters as needed. Bug: 1218540,1485598 Change-Id: I3d956f5f2cd54a5da76a20e7d63411b3b7fc51ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4879582 Reviewed-by: Philip Rogers <pdr@chromium.org> Commit-Queue: Cammie Smith Barnes <cammie@chromium.org> Reviewed-by: Ayu Ishii <ayui@chromium.org> Reviewed-by: Garrett Tanzer <gtanzer@chromium.org> Reviewed-by: Avi Drissman <avi@chromium.org> Reviewed-by: danakj <danakj@chromium.org> Reviewed-by: Yao Xiao <yaoxia@chromium.org> Cr-Commit-Position: refs/heads/main@{#1204170} -- wpt-commits: 25ddb07c3be61b730b94a7ff1bc17f5a4c7c1be2 wpt-pr: 42224
moz-v2v-gh
pushed a commit
to mozilla/gecko-dev
that referenced
this pull request
Oct 6, 2023
…o per-site budgets, a=testonly Automatic update from web-platform-tests Shared Storage: Change from per-origin to per-site budgets We update to using per-site privacy budgets instead of per-origin privacy budgets. This will align with enrollment enforcement, which is per-site. See also WICG/shared-storage#112 and WICG/shared-storage#118. To accomplish this, we migrate the `SharedStorageDatabase` to version 4, where the `budget_mapping` table's `context_origin` column has been renamed to `context_site`, and any existing data for version 3 databases will have each serialized origin in that column replaced by the corresponding serialization of the origin's site. We also update the names and types of other members and parameters as needed. Bug: 1218540,1485598 Change-Id: I3d956f5f2cd54a5da76a20e7d63411b3b7fc51ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4879582 Reviewed-by: Philip Rogers <pdr@chromium.org> Commit-Queue: Cammie Smith Barnes <cammie@chromium.org> Reviewed-by: Ayu Ishii <ayui@chromium.org> Reviewed-by: Garrett Tanzer <gtanzer@chromium.org> Reviewed-by: Avi Drissman <avi@chromium.org> Reviewed-by: danakj <danakj@chromium.org> Reviewed-by: Yao Xiao <yaoxia@chromium.org> Cr-Commit-Position: refs/heads/main@{#1204170} -- wpt-commits: 25ddb07c3be61b730b94a7ff1bc17f5a4c7c1be2 wpt-pr: 42224
jamienicol
pushed a commit
to jamienicol/gecko
that referenced
this pull request
Oct 6, 2023
…o per-site budgets, a=testonly Automatic update from web-platform-tests Shared Storage: Change from per-origin to per-site budgets We update to using per-site privacy budgets instead of per-origin privacy budgets. This will align with enrollment enforcement, which is per-site. See also WICG/shared-storage#112 and WICG/shared-storage#118. To accomplish this, we migrate the `SharedStorageDatabase` to version 4, where the `budget_mapping` table's `context_origin` column has been renamed to `context_site`, and any existing data for version 3 databases will have each serialized origin in that column replaced by the corresponding serialization of the origin's site. We also update the names and types of other members and parameters as needed. Bug: 1218540,1485598 Change-Id: I3d956f5f2cd54a5da76a20e7d63411b3b7fc51ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4879582 Reviewed-by: Philip Rogers <pdr@chromium.org> Commit-Queue: Cammie Smith Barnes <cammie@chromium.org> Reviewed-by: Ayu Ishii <ayui@chromium.org> Reviewed-by: Garrett Tanzer <gtanzer@chromium.org> Reviewed-by: Avi Drissman <avi@chromium.org> Reviewed-by: danakj <danakj@chromium.org> Reviewed-by: Yao Xiao <yaoxia@chromium.org> Cr-Commit-Position: refs/heads/main@{#1204170} -- wpt-commits: 25ddb07c3be61b730b94a7ff1bc17f5a4c7c1be2 wpt-pr: 42224
jamienicol
pushed a commit
to jamienicol/gecko
that referenced
this pull request
Oct 6, 2023
…o per-site budgets, a=testonly Automatic update from web-platform-tests Shared Storage: Change from per-origin to per-site budgets We update to using per-site privacy budgets instead of per-origin privacy budgets. This will align with enrollment enforcement, which is per-site. See also WICG/shared-storage#112 and WICG/shared-storage#118. To accomplish this, we migrate the `SharedStorageDatabase` to version 4, where the `budget_mapping` table's `context_origin` column has been renamed to `context_site`, and any existing data for version 3 databases will have each serialized origin in that column replaced by the corresponding serialization of the origin's site. We also update the names and types of other members and parameters as needed. Bug: 1218540,1485598 Change-Id: I3d956f5f2cd54a5da76a20e7d63411b3b7fc51ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4879582 Reviewed-by: Philip Rogers <pdr@chromium.org> Commit-Queue: Cammie Smith Barnes <cammie@chromium.org> Reviewed-by: Ayu Ishii <ayui@chromium.org> Reviewed-by: Garrett Tanzer <gtanzer@chromium.org> Reviewed-by: Avi Drissman <avi@chromium.org> Reviewed-by: danakj <danakj@chromium.org> Reviewed-by: Yao Xiao <yaoxia@chromium.org> Cr-Commit-Position: refs/heads/main@{#1204170} -- wpt-commits: 25ddb07c3be61b730b94a7ff1bc17f5a4c7c1be2 wpt-pr: 42224
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-wordified-and-comments-removed
that referenced
this pull request
Oct 13, 2023
…o per-site budgets, a=testonly Automatic update from web-platform-tests Shared Storage: Change from per-origin to per-site budgets We update to using per-site privacy budgets instead of per-origin privacy budgets. This will align with enrollment enforcement, which is per-site. See also WICG/shared-storage#112 and WICG/shared-storage#118. To accomplish this, we migrate the `SharedStorageDatabase` to version 4, where the `budget_mapping` table's `context_origin` column has been renamed to `context_site`, and any existing data for version 3 databases will have each serialized origin in that column replaced by the corresponding serialization of the origin's site. We also update the names and types of other members and parameters as needed. Bug: 1218540,1485598 Change-Id: I3d956f5f2cd54a5da76a20e7d63411b3b7fc51ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4879582 Reviewed-by: Philip Rogers <pdrchromium.org> Commit-Queue: Cammie Smith Barnes <cammiechromium.org> Reviewed-by: Ayu Ishii <ayuichromium.org> Reviewed-by: Garrett Tanzer <gtanzerchromium.org> Reviewed-by: Avi Drissman <avichromium.org> Reviewed-by: danakj <danakjchromium.org> Reviewed-by: Yao Xiao <yaoxiachromium.org> Cr-Commit-Position: refs/heads/main{#1204170} -- wpt-commits: 25ddb07c3be61b730b94a7ff1bc17f5a4c7c1be2 wpt-pr: 42224 UltraBlame original commit: 4cf5d5161ed3fad2a643c76f1f252d036b91d661
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-wordified-and-comments-removed
that referenced
this pull request
Oct 13, 2023
…o per-site budgets, a=testonly Automatic update from web-platform-tests Shared Storage: Change from per-origin to per-site budgets We update to using per-site privacy budgets instead of per-origin privacy budgets. This will align with enrollment enforcement, which is per-site. See also WICG/shared-storage#112 and WICG/shared-storage#118. To accomplish this, we migrate the `SharedStorageDatabase` to version 4, where the `budget_mapping` table's `context_origin` column has been renamed to `context_site`, and any existing data for version 3 databases will have each serialized origin in that column replaced by the corresponding serialization of the origin's site. We also update the names and types of other members and parameters as needed. Bug: 1218540,1485598 Change-Id: I3d956f5f2cd54a5da76a20e7d63411b3b7fc51ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4879582 Reviewed-by: Philip Rogers <pdrchromium.org> Commit-Queue: Cammie Smith Barnes <cammiechromium.org> Reviewed-by: Ayu Ishii <ayuichromium.org> Reviewed-by: Garrett Tanzer <gtanzerchromium.org> Reviewed-by: Avi Drissman <avichromium.org> Reviewed-by: danakj <danakjchromium.org> Reviewed-by: Yao Xiao <yaoxiachromium.org> Cr-Commit-Position: refs/heads/main{#1204170} -- wpt-commits: 25ddb07c3be61b730b94a7ff1bc17f5a4c7c1be2 wpt-pr: 42224 UltraBlame original commit: 679462d3a7918390311e4b11a58dcabb09cd72e2
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-comments-removed
that referenced
this pull request
Oct 13, 2023
…o per-site budgets, a=testonly Automatic update from web-platform-tests Shared Storage: Change from per-origin to per-site budgets We update to using per-site privacy budgets instead of per-origin privacy budgets. This will align with enrollment enforcement, which is per-site. See also WICG/shared-storage#112 and WICG/shared-storage#118. To accomplish this, we migrate the `SharedStorageDatabase` to version 4, where the `budget_mapping` table's `context_origin` column has been renamed to `context_site`, and any existing data for version 3 databases will have each serialized origin in that column replaced by the corresponding serialization of the origin's site. We also update the names and types of other members and parameters as needed. Bug: 1218540,1485598 Change-Id: I3d956f5f2cd54a5da76a20e7d63411b3b7fc51ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4879582 Reviewed-by: Philip Rogers <pdrchromium.org> Commit-Queue: Cammie Smith Barnes <cammiechromium.org> Reviewed-by: Ayu Ishii <ayuichromium.org> Reviewed-by: Garrett Tanzer <gtanzerchromium.org> Reviewed-by: Avi Drissman <avichromium.org> Reviewed-by: danakj <danakjchromium.org> Reviewed-by: Yao Xiao <yaoxiachromium.org> Cr-Commit-Position: refs/heads/main{#1204170} -- wpt-commits: 25ddb07c3be61b730b94a7ff1bc17f5a4c7c1be2 wpt-pr: 42224 UltraBlame original commit: 4cf5d5161ed3fad2a643c76f1f252d036b91d661
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-comments-removed
that referenced
this pull request
Oct 13, 2023
…o per-site budgets, a=testonly Automatic update from web-platform-tests Shared Storage: Change from per-origin to per-site budgets We update to using per-site privacy budgets instead of per-origin privacy budgets. This will align with enrollment enforcement, which is per-site. See also WICG/shared-storage#112 and WICG/shared-storage#118. To accomplish this, we migrate the `SharedStorageDatabase` to version 4, where the `budget_mapping` table's `context_origin` column has been renamed to `context_site`, and any existing data for version 3 databases will have each serialized origin in that column replaced by the corresponding serialization of the origin's site. We also update the names and types of other members and parameters as needed. Bug: 1218540,1485598 Change-Id: I3d956f5f2cd54a5da76a20e7d63411b3b7fc51ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4879582 Reviewed-by: Philip Rogers <pdrchromium.org> Commit-Queue: Cammie Smith Barnes <cammiechromium.org> Reviewed-by: Ayu Ishii <ayuichromium.org> Reviewed-by: Garrett Tanzer <gtanzerchromium.org> Reviewed-by: Avi Drissman <avichromium.org> Reviewed-by: danakj <danakjchromium.org> Reviewed-by: Yao Xiao <yaoxiachromium.org> Cr-Commit-Position: refs/heads/main{#1204170} -- wpt-commits: 25ddb07c3be61b730b94a7ff1bc17f5a4c7c1be2 wpt-pr: 42224 UltraBlame original commit: 679462d3a7918390311e4b11a58dcabb09cd72e2
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-wordified
that referenced
this pull request
Oct 13, 2023
…o per-site budgets, a=testonly Automatic update from web-platform-tests Shared Storage: Change from per-origin to per-site budgets We update to using per-site privacy budgets instead of per-origin privacy budgets. This will align with enrollment enforcement, which is per-site. See also WICG/shared-storage#112 and WICG/shared-storage#118. To accomplish this, we migrate the `SharedStorageDatabase` to version 4, where the `budget_mapping` table's `context_origin` column has been renamed to `context_site`, and any existing data for version 3 databases will have each serialized origin in that column replaced by the corresponding serialization of the origin's site. We also update the names and types of other members and parameters as needed. Bug: 1218540,1485598 Change-Id: I3d956f5f2cd54a5da76a20e7d63411b3b7fc51ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4879582 Reviewed-by: Philip Rogers <pdrchromium.org> Commit-Queue: Cammie Smith Barnes <cammiechromium.org> Reviewed-by: Ayu Ishii <ayuichromium.org> Reviewed-by: Garrett Tanzer <gtanzerchromium.org> Reviewed-by: Avi Drissman <avichromium.org> Reviewed-by: danakj <danakjchromium.org> Reviewed-by: Yao Xiao <yaoxiachromium.org> Cr-Commit-Position: refs/heads/main{#1204170} -- wpt-commits: 25ddb07c3be61b730b94a7ff1bc17f5a4c7c1be2 wpt-pr: 42224 UltraBlame original commit: 4cf5d5161ed3fad2a643c76f1f252d036b91d661
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-wordified
that referenced
this pull request
Oct 13, 2023
…o per-site budgets, a=testonly Automatic update from web-platform-tests Shared Storage: Change from per-origin to per-site budgets We update to using per-site privacy budgets instead of per-origin privacy budgets. This will align with enrollment enforcement, which is per-site. See also WICG/shared-storage#112 and WICG/shared-storage#118. To accomplish this, we migrate the `SharedStorageDatabase` to version 4, where the `budget_mapping` table's `context_origin` column has been renamed to `context_site`, and any existing data for version 3 databases will have each serialized origin in that column replaced by the corresponding serialization of the origin's site. We also update the names and types of other members and parameters as needed. Bug: 1218540,1485598 Change-Id: I3d956f5f2cd54a5da76a20e7d63411b3b7fc51ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4879582 Reviewed-by: Philip Rogers <pdrchromium.org> Commit-Queue: Cammie Smith Barnes <cammiechromium.org> Reviewed-by: Ayu Ishii <ayuichromium.org> Reviewed-by: Garrett Tanzer <gtanzerchromium.org> Reviewed-by: Avi Drissman <avichromium.org> Reviewed-by: danakj <danakjchromium.org> Reviewed-by: Yao Xiao <yaoxiachromium.org> Cr-Commit-Position: refs/heads/main{#1204170} -- wpt-commits: 25ddb07c3be61b730b94a7ff1bc17f5a4c7c1be2 wpt-pr: 42224 UltraBlame original commit: 679462d3a7918390311e4b11a58dcabb09cd72e2
Lightning00Blade
pushed a commit
to Lightning00Blade/wpt
that referenced
this pull request
Dec 11, 2023
We update to using per-site privacy budgets instead of per-origin privacy budgets. This will align with enrollment enforcement, which is per-site. See also WICG/shared-storage#112 and WICG/shared-storage#118. To accomplish this, we migrate the `SharedStorageDatabase` to version 4, where the `budget_mapping` table's `context_origin` column has been renamed to `context_site`, and any existing data for version 3 databases will have each serialized origin in that column replaced by the corresponding serialization of the origin's site. We also update the names and types of other members and parameters as needed. Bug: 1218540,1485598 Change-Id: I3d956f5f2cd54a5da76a20e7d63411b3b7fc51ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4879582 Reviewed-by: Philip Rogers <pdr@chromium.org> Commit-Queue: Cammie Smith Barnes <cammie@chromium.org> Reviewed-by: Ayu Ishii <ayui@chromium.org> Reviewed-by: Garrett Tanzer <gtanzer@chromium.org> Reviewed-by: Avi Drissman <avi@chromium.org> Reviewed-by: danakj <danakj@chromium.org> Reviewed-by: Yao Xiao <yaoxia@chromium.org> Cr-Commit-Position: refs/heads/main@{#1204170}
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.
We update the spec to reflect the explainer changes landed in PR #112 .
We are now going to use per-site privacy budgets instead of per-origin privacy budgets. This will better align with enrollment enforcement, which is also per-site.
Preview | Diff