DBSC Newsletter | March 2025
dbsc-announce
Spec
We’re excited to announce that we have been accepted into the Web Application Security Working Group! Accordingly, the draft spec for DBSC has been moved to https://w3c.github.io/webappsec-dbsc/. Please continue to review and provide feedback, comments and questions.
DBSC Components Status Updates
Registration: Completed
Create sessions: Completed
Persistence: Completed
Refreshes: Completed
Note that currently refreshes block requests. Proactive refreshes will be worked on after origin trials.
Clearing sessions: Completed
Netlogging: Completed
Spec: In progress - Completed first draft expected by the end of 2025 Q1
Web Platform tests: In progress - completion expected by the end 2025 Q1
Dev tools: Not started - will be starting implementation in 2025 Q2
Note that this will not be available for origin trials.
DBSC is currently ready for early developer testing. Please refer to https://github.com/w3c/webappsec-dbsc/wiki/Testing-early-versions-of-DBSC for all the details on how to test the protocol. Note that some of the flags may be changing due to ongoing work, we’ll send an announcement to this group if that happens. You can always refer back to the testing link above to ensure you have the latest instructions in case you run into any errors.
We had a few delays and had to move the DBSC origin trials from M134 to M135 (to be confirmed). If M135 is accepted, these will be the new dates for the release:
Beta: March 5, 2025 (new)
Stable: April 1, 2025
We’ll send another update once we get confirmed on the exact milestone for origin trials.
For those of you new to origin trials refer to this getting started guide on how they are conducted and what to expect. For DBSC, we’re planning to conduct two separate origin trials to gather specific feedback on different parts of the protocol. However, do not feel limited to providing feedback on the following specific topics! We value any feedback about DBSC at any time as we want to make this protocol accessible and useful for everyone.
Origin Trial 1
Overview: General functionality of protocol and its APIs.
Length: ~6 months
Feedback type requested: Functionality, compatibility your service, developer experience with integration, user experience changes, performance
Origin Trial 2
Overview: Reliability of the protocol
Length: ~3 months
Feedback type requested: Stability, user sign out rates, notable errors
More platform support
After origin trials we’ll be prioritizing adding support for the following platforms in this order:
macOS
ChromeOS
Linux
Proactive refreshes
The specification leaves room for Chrome to notice that a bound cookie is about to expire while the site is still open, and refresh it before the cookie actually expires. This would eliminate the latency cost of a blocking refresh request for sites with long-term usage.
Community feature requests and support
As always, we’ll be monitoring the github issue tracker for important feature requests and bugs and will be prioritizing them accordingly.
If you have any questions or comments, please reach out on the github project.
Thanks
DBSC team