If anyone wants to see these protections in action, www.clerk.dev leverages the Storage Access API in development mode - where we need to share session data across localhost and a clerk-owned domain.
With this launch, developers are now prompted to explicitly allow third-party cookie access in Firefox.
(In production mode, the prompt isn't thrown because our cookies are set in a first party context.)
If anyone wants to see these protections in action, www.clerk.dev leverages the Storage Access API in development mode - where we need to share session data across localhost and a clerk-owned domain.
With this launch, developers are now prompted to explicitly allow third-party cookie access in Firefox.
(In production mode, the prompt isn't thrown because our cookies are set in a first party context.)