こんにちは TAG-さん!

I'm requesting an early TAG design review for renaming the Storage Access handle methods for non-cookie StorageAccessAPI.

Based on community feedback we would like to rename the BroadcastChannel() and SharedWorker() methods on the Storage Access Handle to be createBroadcastChannel() and createSharedWorker() to better distinguish between the storage constructor class names and the handle methods

• Explainer¹: N/A

• User research: N/A

• Security and Privacy self-review²: N/A, method name change with no privacy/security impact

• GitHub repo: https://github.com/privacycg/saa-non-cookie-storage

• Primary contacts:

  • @cfredric, Google
  • @aamuley, Google

• Organization/project driving the design: Privacy Sandbox

• This work is being funded by: Google

• Incubation and standards groups that have discussed the design:

  • PrivacyCG https://github.com/privacycg/saa-non-cookie-storage/issues/31

• Standards group(s) that you expect to discuss and/or adopt this work when it's ready: PrivacyCG

• Multi-stakeholder feedback³:

  • Chromium comments: Positive

  • Mozilla comments: https://github.com/mozilla/standards-positions/issues/1226

  • WebKit comments: https://github.com/WebKit/standards-positions/issues/491 https://github.com/privacycg/saa-non-cookie-storage/issues/31#issuecomment-2738457524

  • {{...include feedback/review from developers, implementers, civil society, and others}}

• Major unresolved issues with or opposition to this design:

• I have reviewed the TAG's Web Platform Design Principles

You should also know that...

<!------------------------------------------------------------------------------------