Privacy Community Group - Activity in 2024
No matches.
Participants
-
2 participants joined.
-
Tom Ritter (Mozilla Foundation) joined.
-
Magnus Jurdal joined.
-
-
5 participants left.
-
Mallory Knodel (Center for Democracy and Technology) left.
-
Wendell Baker (Yahoo Holdings Inc.) left.
-
Eyal Abadi (Procter & Gamble) left.
-
Daniel LaLiberte (Google LLC) left.
-
Magnus Jurdal left.
-
GitHub
privacycg/proposals
-
1 issue received 1 new comment.
privacycg/.github
-
1 pull request opened.
-
Create devcontainer.json privacycg/.github#7, by @developer982.
-
-
1 pull request closed.
-
Create devcontainer.json privacycg/.github#7.
-
privacycg/storage-partitioning
-
1 pull request received 1 new comment.
privacycg/storage-access-headers
-
1 issue opened.
-
Should `retry` use a different name/keyword? privacycg/storage-access-headers#23, by @cfredric.
-
-
3 issues closed.
-
Consider interaction with Storage partitioning privacycg/storage-access-headers#1.
-
An inactive-retry-active flow should be transparent for the embedder privacycg/storage-access-headers#10.
-
Clarify `retry` semantics w.r.t. HTTP auth and redirects privacycg/storage-access-headers#12.
-
-
4 issues received 7 new comments.
-
Network roundtrips doubled for API requests privacycg/storage-access-headers#6 (3 comments by @petipp, @sandormajor)
-
Should `retry` use a different name/keyword? privacycg/storage-access-headers#23 (2 comments by @bvandersloot-mozilla, @cfredric)
-
An inactive-retry-active flow should be transparent for the embedder privacycg/storage-access-headers#10 (1 comment by @cfredric)
-
Clarify `retry` semantics w.r.t. HTTP auth and redirects privacycg/storage-access-headers#12 (1 comment by @cfredric)
-
-
1 pull request opened.
-
Storage access activation reusability privacycg/storage-access-headers#22, by @sandormajor.
-
-
1 pull request merged.
-
Replace embedded sequence diagrams with mermaid code privacycg/storage-access-headers#21.
-
-
2 pull requests received 9 new comments.
-
Replace embedded sequence diagrams with mermaid code privacycg/storage-access-headers#21 (1 comment by @sandormajor)
privacycg/CHIPS
-
1 issue opened.
-
Clear-Site-Data integration is incorrect privacycg/CHIPS#93, by @annevk.
-
-
2 issues received 2 new comments.
-
Decide if the top-level document's origin's port should be part of the partition key privacycg/CHIPS#92 (1 comment by @Sora2455)
-
How do `Partitioned` cookies interact with browser extensions? privacycg/CHIPS#6 (1 comment by @aselya)
-
privacycg/storage-access
-
2 issues opened.
-
fileMipo.01 privacycg/storage-access#212, by @Ppeepost4489.
-
F2-New privacycg/storage-access#211, by @Ppeepost4489.
-
-
2 issues closed.
-
F2-New privacycg/storage-access#211.
-
fileMipo.01 privacycg/storage-access#212.
-
-
2 issues received 8 new comments.
-
`environment/has storage access` is not cleared during cross-site redirects privacycg/storage-access#210 (7 comments by @annevk, @bvandersloot-mozilla, @cfredric, @HeikoTheissen, @johannhof)
-
Make implicit deny and explicit deny indistinguishable privacycg/storage-access#60 (1 comment by @Ppeepost4489)
-
privacycg/nav-tracking-mitigations
-
1 issue received 2 new comments.
-
Bounce tracking should mitigate etag/Last-Modified tracking of http cache resources privacycg/nav-tracking-mitigations#41 (2 comments by @MrPickles, @Trikolon)
-
Participants
-
4 participants joined.
-
Andrew Knox (Google LLC) joined.
-
Saatvika Sathi joined.
-
Saatvika Sathi joined.
-
Tara Tarakiyee (Sovereign Tech Fund) joined.
-
-
4 participants left.
-
Joey Stanford (Platform.sh) left.
-
Andrew Knox (Google LLC) left.
-
Chinmay Abhay Nerurkar (Microsoft Corporation) left.
-
Saatvika Sathi left.
-
-
1 organization joined.
-
Sovereign Tech Fund joined.
-
-
1 organization left.
-
Platform.sh left.
-
GitHub
privacycg/nav-tracking-mitigations
-
1 issue received 1 new comment.
-
Bounce tracking should mitigate etag/Last-Modified tracking of http cache resources privacycg/nav-tracking-mitigations#41 (1 comment by @MrPickles)
-
privacycg/storage-access-headers
-
1 issue received 4 new comments.
-
Network roundtrips doubled for API requests privacycg/storage-access-headers#6 (4 comments by @arturjanc, @petipp, @sandormajor)
-
-
2 pull requests opened.
-
Replace embedded sequence diagrams with mermaid code privacycg/storage-access-headers#21, by @sandormajor.
-
Write specification privacycg/storage-access-headers#20, by @cfredric.
-
-
1 pull request merged.
-
Write specification privacycg/storage-access-headers#20.
-
-
2 pull requests received 102 new comments.
-
Write specification privacycg/storage-access-headers#20 (101 comments by @cfredric, @domfarolino, @johannhof, @MattMenke2, @sandormajor)
-
Replace embedded sequence diagrams with mermaid code privacycg/storage-access-headers#21 (1 comment by @sandormajor)
-
privacycg/storage-access
-
1 issue opened.
-
`environment/has storage access` is not cleared during cross-site redirects privacycg/storage-access#210, by @cfredric.
-
-
2 issues received 5 new comments.
-
`environment/has storage access` is not cleared during cross-site redirects privacycg/storage-access#210 (4 comments by @annevk, @HeikoTheissen, @johannhof)
-
Improving the Storage Access API security model privacycg/storage-access#113 (1 comment by @Omar34483)
-
privacycg/CHIPS
-
1 issue received 3 new comments.
-
Reduce overall per-site per-partition limit to 1 KiB privacycg/CHIPS#74 (3 comments by @annevk, @krgovind, @Sora2455)
-
privacycg/storage-partitioning
-
1 issue received 1 new comment.
Participants
-
5 participants joined.
-
Brian May joined.
-
Aaron Selya (Google LLC) joined.
-
Lee Brewer (Ping Identity) joined.
-
Ushita Deepak Palande (Google LLC) joined.
-
Raphaël Cazenave-Lévêque joined.
-
-
1 participant left.
-
Brian May left.
-
-
1 organization left.
-
Dstillery left.
-
GitHub
privacycg/CHIPS
-
1 issue opened.
-
Decide if the top-level document's origin's port should be part of the partition key privacycg/CHIPS#92, by @Sora2455.
-
-
2 issues received 11 new comments.
-
Decide if the top-level document's origin's port should be part of the partition key privacycg/CHIPS#92 (8 comments by @annevk, @bvandersloot-mozilla, @johannhof, @martinthomson, @Sora2455)
-
How do `Partitioned` cookies interact with browser extensions? privacycg/CHIPS#6 (3 comments by @izogfif, @Rob--W)
-
privacycg/storage-access-headers
-
2 issues opened.
-
Headers may limit possible Storage Access API policies privacycg/storage-access-headers#18, by @sjledoux.
-
The "Sec-" prefix is unnecessary privacycg/storage-access-headers#17, by @sjledoux.
-
-
2 issues closed.
-
Headers may limit possible Storage Access API policies privacycg/storage-access-headers#18.
-
The "Sec-" prefix is unnecessary privacycg/storage-access-headers#17.
-
-
2 issues received 7 new comments.
-
The "Sec-" prefix is unnecessary privacycg/storage-access-headers#17 (5 comments by @cfredric, @johannhof, @jyasskin)
-
Headers may limit possible Storage Access API policies privacycg/storage-access-headers#18 (2 comments by @cfredric, @jyasskin)
-
-
1 pull request opened.
-
Remove redundant detail in example privacycg/storage-access-headers#19, by @sandormajor.
-
-
1 pull request merged.
-
Remove redundant detail in example privacycg/storage-access-headers#19.
-
-
1 pull request received 1 new comment.
privacycg/nav-tracking-mitigations
-
2 issues closed.
-
Normative references to discontinued specs in Navigational-Tracking Mitigations privacycg/nav-tracking-mitigations#67.
-
Specify behavior on tab close / destruction of a top level traversable privacycg/nav-tracking-mitigations#83.
-
-
2 issues received 4 new comments.
-
General Navigational Tracking mitigation, lifted from FedCM privacycg/nav-tracking-mitigations#82 (3 comments by @bvandersloot-mozilla, @wanderview)
-
Specify behavior on tab close / destruction of a top level traversable privacycg/nav-tracking-mitigations#83 (1 comment by @svendlarsen)
-
-
7 pull requests opened.
-
Fix logic to add initial host to user activation set privacycg/nav-tracking-mitigations#90, by @amaliev.
-
Fix an incorrect reference to "storage access set" when recording user activation privacycg/nav-tracking-mitigations#89, by @amaliev.
-
Use the latest action runner and checkout action. privacycg/nav-tracking-mitigations#88, by @jyasskin.
-
Test a fix for spec-prod privacycg/nav-tracking-mitigations#87, by @jyasskin.
-
Work around failing bikeshed install on CI privacycg/nav-tracking-mitigations#86, by @svendlarsen.
-
End extended navigation on tab close privacycg/nav-tracking-mitigations#85, by @svendlarsen.
-
Disambiguate `remote end steps` dfn link privacycg/nav-tracking-mitigations#84, by @svendlarsen.
-
-
7 pull requests merged.
-
Fix logic to add initial host to user activation set privacycg/nav-tracking-mitigations#90.
-
Fix an incorrect reference to "storage access set" when recording user activation privacycg/nav-tracking-mitigations#89.
-
Add user activation set to bounce tracking record privacycg/nav-tracking-mitigations#70.
-
Use the latest action runner and checkout action. privacycg/nav-tracking-mitigations#88.
-
End extended navigation on tab close privacycg/nav-tracking-mitigations#85.
-
Disambiguate `remote end steps` dfn link privacycg/nav-tracking-mitigations#84.
-
Work around failing bikeshed install on CI privacycg/nav-tracking-mitigations#86.
-
-
1 pull request closed.
-
Test a fix for spec-prod privacycg/nav-tracking-mitigations#87.
-
-
3 pull requests received 11 new comments.
-
Disambiguate `remote end steps` dfn link privacycg/nav-tracking-mitigations#84 (6 comments by @jyasskin, @svendlarsen, @wanderview)
-
End extended navigation on tab close privacycg/nav-tracking-mitigations#85 (4 comments by @svendlarsen, @wanderview)
-
Work around failing bikeshed install on CI privacycg/nav-tracking-mitigations#86 (1 comment by @wanderview)
-
privacycg/storage-access
-
1 issue opened.
-
> This would be for sites on some kind of tracking list that start out without any kind of storage? Because I think ideally this would be the default. (Even more ideal would be if we didn't need the lists long term as the partitioning would keep it all in check.) privacycg/storage-access#208, by @patrron.
-
-
1 issue closed.
-
3 issues reopened.
-
> This would be for sites on some kind of tracking list that start out without any kind of storage? Because I think ideally this would be the default. (Even more ideal would be if we didn't need the lists long term as the partitioning would keep it all in check.) privacycg/storage-access#208, by @johannhof.
-
> This would be for sites on some kind of tracking list that start out without any kind of storage? Because I think ideally this would be the default. (Even more ideal would be if we didn't need the lists long term as the partitioning would keep it all in check.) privacycg/storage-access#208, by @patrron.
-
> This would be for sites on some kind of tracking list that start out without any kind of storage? Because I think ideally this would be the default. (Even more ideal would be if we didn't need the lists long term as the partitioning would keep it all in check.) privacycg/storage-access#208, by @patrron.
-
-
1 pull request opened.
-
Update Chromium's implementation location in comment privacycg/storage-access#207, by @cfredric.
-
-
2 pull requests merged.
-
Update Chromium's implementation location in comment privacycg/storage-access#207.
-
Modify spec to incorporate storage-access-for-fedcm proposal privacycg/storage-access#206.
-
-
2 pull requests received 10 new comments.
-
Modify spec to incorporate storage-access-for-fedcm proposal privacycg/storage-access#206 (9 comments by @cfredric, @johannhof)
-
Update Chromium's implementation location in comment privacycg/storage-access#207 (1 comment by @johannhof)
-
privacycg/meetings
-
1 issue closed.
-
TPAC 2024 privacycg/meetings#38.
-
privacycg/privacycg.github.io
-
1 issue closed.
-
Drop Melanie from the list of isLoggedIn editors. privacycg/privacycg.github.io#35.
-
-
1 issue received 1 new comment.
-
Drop Melanie from the list of isLoggedIn editors. privacycg/privacycg.github.io#35 (1 comment by @martinthomson)
-
-
2 pull requests opened.
-
Fix numbers privacycg/privacycg.github.io#46, by @martinthomson.
-
List the extra repos privacycg/privacycg.github.io#45, by @martinthomson.
-
-
3 pull requests merged.
-
Editor updates privacycg/privacycg.github.io#41.
-
Fix numbers privacycg/privacycg.github.io#46.
-
Explicitly number the sections of the charter. privacycg/privacycg.github.io#34.
-
-
1 pull request closed.
-
Add GPC to work items privacycg/privacycg.github.io#42.
-
-
5 pull requests received 8 new comments.
-
Login status is apparently now in FedID WG privacycg/privacycg.github.io#43 (2 comments by @erik-anderson, @samuelgoto)
-
Explicitly number the sections of the charter. privacycg/privacycg.github.io#34 (1 comment by @martinthomson)
Past meetings
Participants
-
7 participants joined.
-
Prakhar Mittal (Google LLC) joined.
-
Ty Everett (BSV Association) joined.
-
Kabul Kurniawan joined.
-
Sandor Major (Google LLC) joined.
-
Zachary Cancio (Google LLC) joined.
-
Fabian Höring (Criteo) joined.
-
Tara Whalen (W3C) joined.
-
-
8 participants left.
-
David Singer (Apple Inc.) left.
-
Vibha Sethi (Yahoo Holdings Inc.) left.
-
Kabul Kurniawan left.
-
Deyu Tian left.
-
Shubhie Panicker (Google LLC) left.
-
Christina Ilvento (Google LLC) left.
-
Tzviya Siegman (Wiley) left.
-
Tara Whalen (W3C) left.
-
-
1 organization joined.
-
BSV Association joined.
-
GitHub
privacycg/CHIPS
-
1 issue opened.
-
CHIPS changing with new path forward? privacycg/CHIPS#91, by @dmdabbs.
-
-
1 issue closed.
-
CHIPS changing with new path forward? privacycg/CHIPS#91.
-
-
3 issues received 6 new comments.
-
Update from non-Chrome browsers on support stance privacycg/CHIPS#66 (4 comments by @annevk, @johnwilander, @miskr-instructure)
-
Safely migrating existing web app cookies to Partitioned privacycg/CHIPS#78 (1 comment by @samdutton)
-
-
1 pull request opened.
-
Update editors list privacycg/CHIPS#90, by @krgovind.
-
-
1 pull request merged.
-
Update editors list privacycg/CHIPS#90.
-
-
1 pull request received 1 new comment.
privacycg/proposals
-
1 issue opened.
-
Cookie Consent Management privacycg/proposals#48, by @frostaloha.
-
-
1 issue received 1 new comment.
privacycg/privacycg.github.io
-
3 pull requests opened.
-
Update CHIPS editors list privacycg/privacycg.github.io#44, by @krgovind.
-
Login status is apparently now in FedID WG privacycg/privacycg.github.io#43, by @martinthomson.
-
Add GPC to work items privacycg/privacycg.github.io#42, by @martinthomson.
-
-
1 pull request merged.
-
Update CHIPS editors list privacycg/privacycg.github.io#44.
-
-
2 pull requests received 2 new comments.
-
Login status is apparently now in FedID WG privacycg/privacycg.github.io#43 (1 comment by @samuelgoto)
privacycg/nav-tracking-mitigations
-
2 issues opened.
-
Specify behavior on tab close / destruction of a top level traversable privacycg/nav-tracking-mitigations#83, by @Trikolon.
-
General Navigational Tracking mitigation, lifted from FedCM privacycg/nav-tracking-mitigations#82, by @bvandersloot-mozilla.
-
-
1 issue received 4 new comments.
-
General Navigational Tracking mitigation, lifted from FedCM privacycg/nav-tracking-mitigations#82 (4 comments by @bvandersloot-mozilla, @johannhof, @martinthomson, @wanderview)
-
privacycg/meetings
-
1 issue received 2 new comments.
privacycg/saa-non-cookie-storage
-
1 issue closed.
-
BroadcastChannel without test-third-party-cookie-phaseout privacycg/saa-non-cookie-storage#27.
-
privacycg/storage-access-headers
-
1 issue opened.
-
Clarify: why is `load` required in addition to `retry`? privacycg/storage-access-headers#16, by @drmercer-lucid.
-
-
4 issues closed.
-
Clarify: why is `load` required in addition to `retry`? privacycg/storage-access-headers#16.
-
Consider restricting leakier no-cors requests to not use these headers privacycg/storage-access-headers#8.
-
Document security caveats of setting the `Activate-Storage-Access: retry` header privacycg/storage-access-headers#7.
-
Sending `Sec-Fetch-Storage-Access: none` on every cross-origin request seems wasteful privacycg/storage-access-headers#15.
-
-
4 issues received 8 new comments.
-
Clarify: why is `load` required in addition to `retry`? privacycg/storage-access-headers#16 (4 comments by @cfredric, @drmercer-lucid)
-
Sending `Sec-Fetch-Storage-Access: none` on every cross-origin request seems wasteful privacycg/storage-access-headers#15 (2 comments by @cfredric)
-
Consider restricting leakier no-cors requests to not use these headers privacycg/storage-access-headers#8 (1 comment by @cfredric)
-
Document security caveats of setting the `Activate-Storage-Access: retry` header privacycg/storage-access-headers#7 (1 comment by @cfredric)
-
privacycg/private-click-measurement
-
1 issue received 1 new comment.
-
Why attribution reports cannot go to third-parties and to anything else than the registrable domain privacycg/private-click-measurement#57 (1 comment by @dule-viant)
-
privacycg/storage-access
-
1 pull request opened.
-
Modify spec to incorporate storage-access-for-fedcm proposal privacycg/storage-access#206, by @cfredric.
-
-
1 pull request merged.
-
Move storage-access-for-fedcm explainer into this repository privacycg/storage-access#204.
-
privacycg/storage-partitioning
-
1 issue received 1 new comment.
privacycg/is-logged-in
-
1 issue received 1 new comment.
Participants
-
6 participants joined.
-
Manuel Bucher (Mozilla Foundation) joined.
-
Andrew Frost (Aloha Browser) joined.
-
Laurent Bertrand joined.
-
Erica Kovac (Google LLC) joined.
-
Jae Li joined.
-
Shannon Roddy (Lawrence Berkeley National Laboratory) joined.
-
-
2 participants left.
-
Merric Moon (Moon Enterprise) left.
-
Shannon Roddy (Lawrence Berkeley National Laboratory) left.
-
-
2 organizations joined.
-
Aloha Browser joined.
-
Lawrence Berkeley National Laboratory joined.
-
-
2 organizations left.
-
Moon Enterprise left.
-
University of California, Berkeley left.
-
GitHub
privacycg/nav-tracking-mitigations
-
1 issue opened.
-
bounce privacycg/nav-tracking-mitigations#81, by @Starr2024.
-
-
1 issue closed.
-
bounce privacycg/nav-tracking-mitigations#81.
-
privacycg/storage-access-headers
-
1 issue opened.
-
Sending `Sec-Fetch-Storage-Access: none` on every cross-origin request seems wasteful privacycg/storage-access-headers#15, by @ricea.
-
-
1 issue received 3 new comments.
-
Sending `Sec-Fetch-Storage-Access: none` on every cross-origin request seems wasteful privacycg/storage-access-headers#15 (3 comments by @HeikoTheissen, @ricea)
-
-
1 pull request merged.
-
Rewrite `retry` token to require an `allowed-origin` parameter privacycg/storage-access-headers#14.
-
privacycg/meetings
privacycg/CHIPS
-
3 issues received 4 new comments.
-
Embedded iframes with different storage access share (and overwrite) the same partitioned cookie privacycg/CHIPS#88 (2 comments by @cfredric, @jsnajdr)
-
Reduce overall per-site per-partition limit to 1 KiB privacycg/CHIPS#74 (1 comment by @longtimelurker)
-
privacycg/is-logged-in
-
1 issue received 3 new comments.
-
Replaced by FedCM login-status API? privacycg/is-logged-in#55 (3 comments by @johnwilander, @samuelgoto)
-
privacycg/storage-partitioning
-
1 issue received 4 new comments.
-
Expose partitionedness privacycg/storage-partitioning#32 (4 comments by @bvandersloot-mozilla, @cfredric)
-
privacycg/storage-access
-
1 issue received 1 new comment.
-
Consider requestStorageAccessFor Method privacycg/storage-access#107 (1 comment by @gladisperezosorio97l)
-
Participants
-
3 participants joined.
-
Jon Matthews (Google LLC) joined.
-
Danielle Bennett joined.
-
shinhwa kim (Google LLC) joined.
-
GitHub
privacycg/storage-partitioning
-
1 issue closed.
-
Accessing session storage in nested documents privacycg/storage-partitioning#42.
-
-
2 issues received 5 new comments.
privacycg/CHIPS
-
1 issue opened.
-
4 issues received 14 new comments.
-
Embedded iframes with different storage access share (and overwrite) the same partitioned cookie privacycg/CHIPS#88 (8 comments by @aselya, @cfredric, @jsnajdr)
-
SameSite attribute handling needs to be clarified privacycg/CHIPS#87 (2 comments by @bvandersloot-mozilla, @kumarrishav)
-
privacycg/storage-access
-
1 issue closed.
-
Offer access to non-partitioned storage somehow privacycg/storage-access#102.
-
-
3 issues received 7 new comments.
-
Top-level calls to navigator.permissions.query for SAA should probably return "granted" privacycg/storage-access#168 (4 comments by @annevk, @johannhof)
-
Expand storage-access-preserving navigations to include same-origin-initiated navigations, not just self-initiated. privacycg/storage-access#197 (2 comments by @cfredric, @jsnajdr)
-
Offer access to non-partitioned storage somehow privacycg/storage-access#102 (1 comment by @johannhof)
-
privacycg/nav-tracking-mitigations
-
2 issues opened.
-
Add dfn links to storage keys' top-level site privacycg/nav-tracking-mitigations#79, by @svendlarsen.
-
Would you review this? (Total Tracking Protection) privacycg/nav-tracking-mitigations#77, by @MasterInQuestion.
-
-
2 issues closed.
-
Delete CHIPS cookies privacycg/nav-tracking-mitigations#75.
-
Would you review this? (Total Tracking Protection) privacycg/nav-tracking-mitigations#77.
-
-
2 issues received 2 new comments.
-
Bounce tracking and technical stability for PETs privacycg/nav-tracking-mitigations#64 (1 comment by @MasterInQuestion)
-
Would you review this? (Total Tracking Protection) privacycg/nav-tracking-mitigations#77 (1 comment by @jyasskin)
-
-
1 pull request opened.
-
Update spec for cookie partition keys and partitioned storage keys privacycg/nav-tracking-mitigations#78, by @svendlarsen.
-
-
1 pull request merged.
-
Update spec for cookie partition keys and partitioned storage keys privacycg/nav-tracking-mitigations#78.
-
-
1 pull request received 21 new comments.
-
Update spec for cookie partition keys and partitioned storage keys privacycg/nav-tracking-mitigations#78 (21 comments by @annevk, @bvandersloot-mozilla, @johannhof, @jyasskin, @svendlarsen, @wanderview)
-
privacycg/storage-access-headers
-
1 issue closed.
-
Already cached responses should not initiate another inactive-retry-active flow privacycg/storage-access-headers#9.
-
-
2 issues received 2 new comments.
-
Already cached responses should not initiate another inactive-retry-active flow privacycg/storage-access-headers#9 (1 comment by @cfredric)
-
Document security caveats of setting the `Activate-Storage-Access: retry` header privacycg/storage-access-headers#7 (1 comment by @cfredric)
-
-
1 pull request opened.
-
Rewrite `retry` token to require an `allowed-origin` parameter privacycg/storage-access-headers#14, by @cfredric.
-
-
1 pull request merged.
-
Add security and privacy self-review privacycg/storage-access-headers#13.
-
Participants
-
1 participant joined.
-
Andrew Chasin (Google LLC) joined.
-
-
2 participants left.
-
Katherine Cheney (Apple Inc.) left.
-
Lisa LeVasseur (Me2B Alliance) left.
-
-
1 organization left.
-
Me2B Alliance left.
-
GitHub
privacycg/storage-access-headers
-
1 issue opened.
-
Clarify `retry` semantics w.r.t. HTTP auth and redirects privacycg/storage-access-headers#12, by @cfredric.
-
-
2 pull requests opened.
-
Add security and privacy self-review privacycg/storage-access-headers#13, by @cfredric.
-
Update details on reasons for cookie access privacycg/storage-access-headers#11, by @cfredric.
-
-
1 pull request merged.
-
Update details on reasons for cookie access privacycg/storage-access-headers#11.
-
-
1 pull request received 5 new comments.
-
Update details on reasons for cookie access privacycg/storage-access-headers#11 (5 comments by @cfredric, @johannhof)
-
privacycg/storage-access
-
1 pull request opened.
-
Move storage-access-for-fedcm explainer into this repository privacycg/storage-access#204, by @johannhof.
-
privacycg/proposals
-
2 issues received 2 new comments.
privacycg/CHIPS
-
1 issue opened.
-
SameSite attribute handling needs to be clarified privacycg/CHIPS#87, by @johannhof.
-
-
4 issues received 14 new comments.
-
Keying of "CHIPS" cookies should align with other state privacycg/CHIPS#40 (7 comments by @aselya, @bvandersloot-mozilla, @HeikoTheissen)
-
Use case for Storage Access API providing access to unpartitioned 1st party cookie privacycg/CHIPS#10 (3 comments by @johannhof, @jsnajdr, @sysrqb)
-
SameSite attribute handling needs to be clarified privacycg/CHIPS#87 (2 comments by @bvandersloot-mozilla, @cfredric)
-
privacycg/saa-non-cookie-storage
-
4 issues opened.
-
Editorial: use dictionary access syntax for accessing properties of dictionaries privacycg/saa-non-cookie-storage#33, by @domenic.
-
Editorial: Constant references to "types" as a variable are confusing privacycg/saa-non-cookie-storage#32, by @domenic.
-
Declaring constructors as methods is strange privacycg/saa-non-cookie-storage#31, by @domenic.
-
design for overload of requestStorageAccess privacycg/saa-non-cookie-storage#30, by @dontcallmedom.
-
-
2 pull requests opened.
-
Make types argument optional privacycg/saa-non-cookie-storage#29, by @dontcallmedom.
-
Set Exposed extended attribute on StorageAccessHandle privacycg/saa-non-cookie-storage#28, by @dontcallmedom.
-
-
1 pull request merged.
-
Set Exposed extended attribute on StorageAccessHandle privacycg/saa-non-cookie-storage#28.
-
-
1 pull request closed.
-
Make types argument optional privacycg/saa-non-cookie-storage#29.
-
-
1 pull request received 2 new comments.
-
Make types argument optional privacycg/saa-non-cookie-storage#29 (2 comments by @arichiv, @dontcallmedom)
-
privacycg/meetings
-
1 issue received 1 new comment.
privacycg/nav-tracking-mitigations
-
2 issues opened.
-
Cross-site subresource tracking vulnerability privacycg/nav-tracking-mitigations#76, by @bvandersloot-mozilla.
-
Delete CHIPS cookies privacycg/nav-tracking-mitigations#75, by @bvandersloot-mozilla.
-
-
2 issues received 3 new comments.
-
Delete CHIPS cookies privacycg/nav-tracking-mitigations#75 (2 comments by @bvandersloot-mozilla, @wanderview)
-
Cross-site subresource tracking vulnerability privacycg/nav-tracking-mitigations#76 (1 comment by @wanderview)
-
GitHub
privacycg/meetings
-
1 issue opened.
-
TPAC 2024 privacycg/meetings#38, by @johannhof.
-
-
8 issues closed.
-
Coordinating sessions with the fedidcg at the W3C TPAC 2022 privacycg/meetings#20.
-
TPAC: Invasive Fingerprinting Protection privacycg/meetings#28.
-
TPAC: state of bounce tracking privacycg/meetings#29.
-
TPAC: heuristics to allow 3P cookies privacycg/meetings#30.
-
TPAC: Storage Access API Graduation privacycg/meetings#31.
-
TPAC: Next steps on Login Status privacycg/meetings#32.
-
TPAC: Storage Access API Future privacycg/meetings#33.
-
TPAC: Pop-up Partitioning / Isolation privacycg/meetings#34.
-
privacycg/CHIPS
-
3 issues received 8 new comments.
-
OIDC authentication on vanity domains with partitioned cookies privacycg/CHIPS#80 (1 comment by @arichiv)
privacycg/proposals
-
2 issues closed.
-
Web hardware revocation API privacycg/proposals#37.
-
FedCM as a trust signal for the Storage Access API privacycg/proposals#46.
-
-
4 issues received 9 new comments.
-
FedCM as a trust signal for the Storage Access API privacycg/proposals#46 (3 comments by @johannhof, @martinthomson)
privacycg/saa-non-cookie-storage
-
1 issue opened.
-
BroadcastChannel without test-third-party-cookie-phaseout privacycg/saa-non-cookie-storage#27, by @antimatter15.
-
-
1 issue received 2 new comments.
-
BroadcastChannel without test-third-party-cookie-phaseout privacycg/saa-non-cookie-storage#27 (2 comments by @arichiv)
-
privacycg/storage-partitioning
-
1 issue received 2 new comments.
-
Consider affordance for embedded frames in extension pages based on externally_connectable privacycg/storage-partitioning#35 (2 comments by @johannhof, @vardhman-singh-glean)
-
-
1 pull request received 1 new comment.
privacycg/storage-access
-
2 issues opened.
-
Unable to acccess third party cookies values - SAP Successfactors, SAP BTP, CHIPS privacycg/storage-access#203, by @Madhumitha2000er.
-
Unable to request storage API access from hosting app to set cookies from iframe privacycg/storage-access#202, by @abhirajdatta.
-
-
1 issue closed.
-
Unable to request storage API access from hosting app to set cookies from iframe privacycg/storage-access#202.
-
-
4 issues received 6 new comments.
-
Unable to request storage API access from hosting app to set cookies from iframe privacycg/storage-access#202 (3 comments by @abhirajdatta, @johannhof)
-
Unable to acccess third party cookies values - SAP Successfactors, SAP BTP, CHIPS privacycg/storage-access#203 (1 comment by @kingcb11)
-
Use case validation - iframe using third party cookies as part of the requests privacycg/storage-access#200 (1 comment by @johannhof)
-
privacycg/template
-
1 issue opened.
-
Root privacycg/template#7, by @don796864.
-
-
1 issue closed.
-
Root privacycg/template#7.
-
-
1 issue received 1 new comment.
privacycg/storage-access-headers
-
2 issues opened.
-
An inactive-retry-active flow should be transparent for the embedder privacycg/storage-access-headers#10, by @dominikschreiber.
-
Already cached responses should not initiate another inactive-retry-active flow privacycg/storage-access-headers#9, by @dominikschreiber.
-
-
1 issue closed.
-
Alternative design: Consider integrating with CORS and HTML and Fetch privacycg/storage-access-headers#3.
-
-
2 issues received 6 new comments.
-
Document security caveats of setting the `Activate-Storage-Access: retry` header privacycg/storage-access-headers#7 (5 comments by @annevk, @cfredric, @johannhof)
-
Alternative design: Consider integrating with CORS and HTML and Fetch privacycg/storage-access-headers#3 (1 comment by @cfredric)
-
Participants
-
4 participants joined.
-
Matthew Atkinson (Samsung Electronics Co., Ltd.) joined.
-
aravindjp Pillai (Preciso) joined.
-
Ruby Rose (Yahoo Holdings Inc.) joined.
-
Achim Schlosser (Bertelsmann SE & Co. KGaA) joined.
-
-
2 participants left.
-
Paul Strobach left.
-
Achim Schlosser (Bertelsmann SE & Co. KGaA) left.
-
-
2 organizations joined.
-
Preciso joined.
-
Bertelsmann SE & Co. KGaA joined.
-
-
1 organization left.
-
European netID Foundation left.
-
GitHub
privacycg/proposals
-
1 issue opened.
-
Pop-up Partitioning privacycg/proposals#47, by @arichiv.
-
privacycg/storage-access
-
1 issue opened.
-
Use case validation - iframe using third party cookies as part of the requests privacycg/storage-access#200, by @carlos-rodrigo.
-
-
2 issues received 2 new comments.
-
Expand storage-access-preserving navigations to include same-origin-initiated navigations, not just self-initiated. privacycg/storage-access#197 (1 comment by @arturjanc)
-
Feature Request: Allow an iframe to request Storage Access permission before the user has visited the origin at the top level privacycg/storage-access#199 (1 comment by @enriquepablo)
-
privacycg/storage-access-headers
-
2 issues opened.
-
Consider restricting leakier no-cors requests to not use these headers privacycg/storage-access-headers#8, by @bvandersloot-mozilla.
-
Document security caveats of setting the `Activate-Storage-Access: retry` header privacycg/storage-access-headers#7, by @arturjanc.
-
-
3 issues received 15 new comments.
-
Alternative design: Consider integrating with CORS and HTML and Fetch privacycg/storage-access-headers#3 (9 comments by @arturjanc, @bvandersloot-mozilla, @cfredric, @johannhof)
-
Consider restricting leakier no-cors requests to not use these headers privacycg/storage-access-headers#8 (3 comments by @arturjanc, @bvandersloot-mozilla)
-
Document security caveats of setting the `Activate-Storage-Access: retry` header privacycg/storage-access-headers#7 (3 comments by @arturjanc, @cfredric, @johannhof)
-
privacycg/nav-tracking-mitigations
-
1 issue received 1 new comment.
-
Enterprise automatic authentication techniques privacycg/nav-tracking-mitigations#36 (1 comment by @iruvinov)
-
privacycg/saa-non-cookie-storage
-
1 issue opened.
-
BroadcastChannel doesn't seem to work privacycg/saa-non-cookie-storage#26, by @antimatter15.
-
-
4 issues closed.
-
Missing BroadcastChannel in Beta 121 privacycg/saa-non-cookie-storage#6.
-
Cross-Domain Local Storage Issue privacycg/saa-non-cookie-storage#14.
-
localStorage handle within iframe is different from localStorage contents of page loaded top-level privacycg/saa-non-cookie-storage#11.
-
BroadcastChannel doesn't seem to work privacycg/saa-non-cookie-storage#26.
-
-
1 issue received 1 new comment.
-
BroadcastChannel doesn't seem to work privacycg/saa-non-cookie-storage#26 (1 comment by @antimatter15)
-
privacycg/CHIPS
-
2 issues received 3 new comments.
-
Clarify behavior when over partition capacity privacycg/CHIPS#85 (2 comments by @bvandersloot-mozilla, @johannhof)
-
How do `Partitioned` cookies interact with browser extensions? privacycg/CHIPS#6 (1 comment by @aselya)
-
-
1 pull request opened.
-
Update CHIPS-tester-list.md privacycg/CHIPS#86, by @ospirito.
-
-
1 pull request merged.
-
Update CHIPS-tester-list.md privacycg/CHIPS#86.
-
-
1 pull request received 2 new comments.
privacycg/storage-partitioning
-
1 issue received 3 new comments.
Participants
-
5 participants joined.
-
Wayne Wang joined.
-
Yue Zhu joined.
-
Oleksandr Yevsieiev (Procter & Gamble) joined.
-
Sophia Cao (RTB House SA) joined.
-
Rhaime Kim (The New York Times) joined.
-
-
3 participants left.
-
Stefano Cossu (J. Paul Getty Trust) left.
-
Philip Lee (Google LLC) left.
-
Chaals Nevile (Consensys) left.
-
GitHub
privacycg/meetings
-
1 pull request merged.
-
Correct comment privacycg/meetings#18.
-
privacycg/saa-non-cookie-storage
-
4 issues opened.
-
Getter substitution is a bit unconventional privacycg/saa-non-cookie-storage#23, by @johannhof.
-
Define SharedWorker usage of SameSiteCookies option privacycg/saa-non-cookie-storage#21, by @arichiv.
-
Cleanup Document Storage Overrides privacycg/saa-non-cookie-storage#19, by @arichiv.
-
Cross-Domain Local Storage Issue privacycg/saa-non-cookie-storage#14, by @CodeKarRohan.
-
-
1 issue closed.
-
Getter substitution is a bit unconventional privacycg/saa-non-cookie-storage#23.
-
-
1 issue reopened.
-
Getter substitution is a bit unconventional privacycg/saa-non-cookie-storage#23, by @arichiv.
-
-
1 issue received 3 new comments.
-
Cross-Domain Local Storage Issue privacycg/saa-non-cookie-storage#14 (3 comments by @arichiv, @johannhof)
-
-
8 pull requests opened.
-
Remove invocation privacycg/saa-non-cookie-storage#25, by @arichiv.
-
Fix Getter Steps privacycg/saa-non-cookie-storage#24, by @arichiv.
-
Fix missing SharedWorker matching criteria privacycg/saa-non-cookie-storage#22, by @arichiv.
-
Add SharedWorkers to spec privacycg/saa-non-cookie-storage#20, by @arichiv.
-
Expand spec with all but SharedWorkers privacycg/saa-non-cookie-storage#18, by @arichiv.
-
Add all/cookies to spec privacycg/saa-non-cookie-storage#17, by @arichiv.
-
Spec Outline privacycg/saa-non-cookie-storage#16, by @arichiv.
-
-
8 pull requests merged.
-
Remove invocation privacycg/saa-non-cookie-storage#25.
-
Fix Getter Steps privacycg/saa-non-cookie-storage#24.
-
Fix missing SharedWorker matching criteria privacycg/saa-non-cookie-storage#22.
-
Add SharedWorkers to spec privacycg/saa-non-cookie-storage#20.
-
Expand spec with all but SharedWorkers privacycg/saa-non-cookie-storage#18.
-
Add all/cookies to spec privacycg/saa-non-cookie-storage#17.
-
Spec Outline privacycg/saa-non-cookie-storage#16.
-
PR test privacycg/saa-non-cookie-storage#15.
-
-
6 pull requests received 27 new comments.
-
Expand spec with all but SharedWorkers privacycg/saa-non-cookie-storage#18 (9 comments by @arichiv, @johannhof)
-
Fix missing SharedWorker matching criteria privacycg/saa-non-cookie-storage#22 (1 comment by @johannhof)
privacycg/proposals
-
1 issue opened.
-
FedCM as a trust signal for the Storage Access API privacycg/proposals#46, by @johannhof.
-
-
1 issue received 1 new comment.
-
FedCM as a trust signal for the Storage Access API privacycg/proposals#46 (1 comment by @bvandersloot-mozilla)
-
privacycg/storage-access
-
2 issues opened.
-
Feature Request: Allow an iframe to request Storage Access permission before the user has visited the origin at the top level privacycg/storage-access#199, by @enriquepablo.
-
Expand storage-access-preserving navigations to include same-origin-initiated navigations, not just self-initiated. privacycg/storage-access#197, by @bvandersloot-mozilla.
-
-
2 issues received 18 new comments.
-
Expand storage-access-preserving navigations to include same-origin-initiated navigations, not just self-initiated. privacycg/storage-access#197 (13 comments by @annevk, @arturjanc, @bvandersloot-mozilla, @cfredric, @johannhof, @jsnajdr)
-
Feature Request: Allow an iframe to request Storage Access permission before the user has visited the origin at the top level privacycg/storage-access#199 (5 comments by @enriquepablo, @johannhof, @johnwilander)
-
privacycg/CHIPS
-
1 issue opened.
-
Clarify behavior when over partition capacity privacycg/CHIPS#85, by @bvandersloot-mozilla.
-
-
3 issues received 4 new comments.
-
Feature request: Opt into origin-partitioned cookies privacycg/CHIPS#83 (2 comments by @annevk, @fscottgaston)
-
OIDC authentication on vanity domains with partitioned cookies privacycg/CHIPS#80 (1 comment by @mefril)
-
privacycg/storage-access-headers
-
1 issue received 6 new comments.
-
Network roundtrips doubled for API requests privacycg/storage-access-headers#6 (6 comments by @arturjanc, @johannhof, @petipp)
-
privacycg/private-click-measurement
-
1 issue received 6 new comments.
-
Send report to both click source and destination privacycg/private-click-measurement#53 (6 comments by @johnwilander, @shoesiq)
-
Participants
-
3 participants joined.
-
Joey Stanford (Platform.sh) joined.
-
Chinmay Abhay Nerurkar (Microsoft Corporation) joined.
-
Simon Hamp joined.
-
-
5 participants left.
-
Joey Stanford (Platform.sh) left.
-
Amanda Tan (AT&T) left.
-
Christopher Wood (Cloudflare) left.
-
Pierre Far (Deliberate Digital Ltd) left.
-
Kiran Gopinath left.
-
-
1 organization joined.
-
Platform.sh joined.
-
-
2 organizations left.
-
Platform left.
-
Deliberate Digital Ltd left.
-
GitHub
privacycg/CHIPS
-
2 issues opened.
-
Servers Partitioning All Cookies privacycg/CHIPS#84, by @volosied.
-
Feature request: Opt into origin-partitioned cookies privacycg/CHIPS#83, by @fscottgaston.
-
-
1 issue closed.
-
Clarify Storage Access API Interaction privacycg/CHIPS#81.
-
-
8 issues received 22 new comments.
-
Feature request: Opt into origin-partitioned cookies privacycg/CHIPS#83 (8 comments by @fscottgaston, @johannhof)
-
How do `Partitioned` cookies interact with browser extensions? privacycg/CHIPS#6 (5 comments by @bvandersloot-mozilla, @DCtheTall, @johannhof, @Rob--W)
-
OIDC authentication on vanity domains with partitioned cookies privacycg/CHIPS#80 (2 comments by @cfredric, @npm1)
-
Clarify Storage Access API Interaction privacycg/CHIPS#81 (2 comments by @bvandersloot-mozilla, @johannhof)
-
privacycg/nav-tracking-mitigations
-
1 issue opened.
-
Service Worker Activation Monkey Patch is out of date privacycg/nav-tracking-mitigations#73, by @bvandersloot-mozilla.
-
privacycg/storage-access-headers
-
1 issue opened.
-
Network roundtrips doubled for API requests privacycg/storage-access-headers#6, by @petipp.
-
-
1 issue received 1 new comment.
-
Network roundtrips doubled for API requests privacycg/storage-access-headers#6 (1 comment by @johannhof)
-
privacycg/storage-access
-
1 issue opened.
-
Support FedCM-based grants privacycg/storage-access#196, by @johannhof.
-
-
4 issues received 14 new comments.
-
How does storage access interact with Dedicated, Shared and Service Workers? privacycg/storage-access#157 (7 comments by @arichiv, @d3lm, @Nemikolh, @wanderview)
-
Offer access to non-partitioned storage somehow privacycg/storage-access#102 (5 comments by @arichiv, @egor-limenko)
-
Potentially specify "prior user interaction" requirement privacycg/storage-access#190 (1 comment by @bvandersloot-mozilla)
-
Let embedees optionally request access to partitioned cookies and storage privacycg/storage-access#75 (1 comment by @h3ku)
-
-
1 pull request merged.
-
document.requestStorageAccess should consider user explicit settings for unpartitioned data access privacycg/storage-access#186.
-
-
1 pull request received 1 new comment.
privacycg/private-click-measurement
-
1 issue opened.
-
Asset Allocation privacycg/private-click-measurement#112, by @LuckyNut12.
-
-
1 issue closed.
-
Asset Allocation privacycg/private-click-measurement#112.
-
privacycg/storage-partitioning
-
2 issues opened.
-
BroadcastChannel being blocked need permissions dialog privacycg/storage-partitioning#44, by @taf2.
-
How to use deprecation trial for unpartitioned third-party storage from an iframe privacycg/storage-partitioning#43, by @Atul22.
-
-
1 issue closed.
-
How to use deprecation trial for unpartitioned third-party storage from an iframe privacycg/storage-partitioning#43.
-
-
1 issue received 25 new comments.
-
BroadcastChannel being blocked need permissions dialog privacycg/storage-partitioning#44 (25 comments by @arichiv, @johannhof, @taf2, @wanderview)
-
Past meetings
-
1 meeting.
Participants
-
10 participants joined.
-
Shannon Roddy (Lawrence Berkeley National Laboratory) joined.
-
Merric Moon (Moon Enterprise) joined.
-
Laura Morinigo (Samsung Electronics Co., Ltd.) joined.
-
Christos Bacharakis (eyeo GmbH) joined.
-
Arthur Coleman joined.
-
Tim Cappalli (Okta) joined.
-
Walter Rudametkin (Inria) joined.
-
Wagner Paz joined.
-
Rushil Walia (Google LLC) joined.
-
Rupert Wiser (Google LLC) joined.
-
-
3 participants left.
-
Arthur Coleman left.
-
Tim Cappalli (Okta) left.
-
Jack Frankland left.
-
-
3 organizations joined.
-
University of California, Berkeley joined.
-
Moon Enterprise joined.
-
Inria joined.
-
GitHub
privacycg/storage-access-headers
-
1 issue opened.
-
Document a [non-iframe] embedded resource flow privacycg/storage-access-headers#4, by @myok12.
-
-
1 issue closed.
-
Document a [non-iframe] embedded resource flow privacycg/storage-access-headers#4.
-
-
3 issues received 8 new comments.
-
Alternative design: Consider integrating with CORS and HTML and Fetch privacycg/storage-access-headers#3 (6 comments by @bvandersloot-mozilla, @cfredric, @johannhof, @Sarrac3873)
-
Document a [non-iframe] embedded resource flow privacycg/storage-access-headers#4 (1 comment by @cfredric)
-
Consider interaction with Storage partitioning privacycg/storage-access-headers#1 (1 comment by @johannhof)
-
privacycg/CHIPS
-
2 issues opened.
-
Clarify Storage Access API Interaction privacycg/CHIPS#81, by @bvandersloot-mozilla.
-
1 issue closed.
-
Safely migrating existing web app cookies to Partitioned privacycg/CHIPS#78.
-
-
7 issues received 18 new comments.
-
Consider supporting partition state in other contexts privacycg/CHIPS#72 (6 comments by @bvandorn, @cfredric, @krgovind)
-
OIDC authentication on vanity domains with partitioned cookies privacycg/CHIPS#80 (5 comments by @krgovind, @mefril, @npm1, @UgoFantozzi)
-
Safely migrating existing web app cookies to Partitioned privacycg/CHIPS#78 (2 comments by @GREsau, @krgovind)
-
Add explicit behavior requirement for "Partitioned" attribute on First Party cookies privacycg/CHIPS#51 (1 comment by @bvandersloot-mozilla)
-
privacycg/storage-access
-
2 issues opened.
-
How can I reset the Storage Access API "previous interaction" state in Chrome? privacycg/storage-access#194, by @DavidScales.
-
server side access (HTTP `Cookie` header) to cookies (`Lax`) inside iframe privacycg/storage-access#193, by @mrksbnch.
-
-
3 issues closed.
-
Possibly don't require user interaction to call requestStorageAccess privacycg/storage-access#192.
-
How can I reset the Storage Access API "previous interaction" state in Chrome? privacycg/storage-access#194.
-
server side access (HTTP `Cookie` header) to cookies (`Lax`) inside iframe privacycg/storage-access#193.
-
-
5 issues received 10 new comments.
-
server side access (HTTP `Cookie` header) to cookies (`Lax`) inside iframe privacycg/storage-access#193 (4 comments by @cfredric, @mrksbnch)
-
How can I reset the Storage Access API "previous interaction" state in Chrome? privacycg/storage-access#194 (2 comments by @cfredric, @johannhof)
-
FR: Request header to indicate storage access privacycg/storage-access#130 (2 comments by @DavidScales, @remko)
-
Possibly don't require user interaction to call requestStorageAccess privacycg/storage-access#192 (1 comment by @annevk)
-
Feature request: Auto-grant storage access without requiring user interaction or explicit API call in cases determined to be safe privacycg/storage-access#170 (1 comment by @DavidScales)
-
-
1 pull request received 1 new comment.
-
document.requestStorageAccess should consider user explicit settings for unpartitioned data access privacycg/storage-access#186 (1 comment by @johannhof)
-
privacycg/nav-tracking-mitigations
-
1 issue opened.
-
Consider how bounce tracking mitigations should interact with private ads API storage privacycg/nav-tracking-mitigations#72, by @wanderview.
-
-
1 issue received 7 new comments.
-
IdP with background sign-in sync: what are the proper white-hat options today? privacycg/nav-tracking-mitigations#69 (7 comments by @BrianLefler, @ondras, @samuelgoto)
-
-
1 pull request received 3 new comments.
-
Add user activation set to bounce tracking record privacycg/nav-tracking-mitigations#70 (3 comments by @jyasskin, @wanderview)
-
privacycg/saa-non-cookie-storage
-
2 issues opened.
-
Possible document.requestStorageAccess.length to return 1 privacycg/saa-non-cookie-storage#12, by @jcubic.
-
localStorage handle within iframe is different from localStorage contents of page loaded top-level privacycg/saa-non-cookie-storage#11, by @antimatter15.
-
-
2 issues closed.
-
detect if document.requestStorageAccess accept argument privacycg/saa-non-cookie-storage#8.
-
Possible document.requestStorageAccess.length to return 1 privacycg/saa-non-cookie-storage#12.
-
-
3 issues received 13 new comments.
-
detect if document.requestStorageAccess accept argument privacycg/saa-non-cookie-storage#8 (7 comments by @arichiv, @jcubic)
-
localStorage handle within iframe is different from localStorage contents of page loaded top-level privacycg/saa-non-cookie-storage#11 (5 comments by @antimatter15, @arichiv)
-
Possible document.requestStorageAccess.length to return 1 privacycg/saa-non-cookie-storage#12 (1 comment by @jcubic)
-
-
1 pull request opened.
-
Add two new extension explainers privacycg/saa-non-cookie-storage#13, by @arichiv.
-
-
1 pull request merged.
-
Add two new extension explainers privacycg/saa-non-cookie-storage#13.
-
privacycg/proposals
-
2 issues received 3 new comments.
-
Extending Storage Access API (SAA) to non-cookie storage privacycg/proposals#41 (1 comment by @arichiv)
privacycg/storage-partitioning
-
1 issue received 1 new comment.
-
Accessing session storage in nested documents privacycg/storage-partitioning#42 (1 comment by @wanderview)
-