We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm filing this issue as a continuation of #3338. There was a lot of conceptual discussion in that issue we've moved on from, and I want to discuss concrete steps to merge https://github.com/privacycg/storage-access into HTML here.
There are still a few remaining issues that the SAA editors would like to see resolved before making a PR: https://github.com/privacycg/storage-access/issues?q=is%3Aissue+is%3Aopen+label%3A%22resolve+before+graduation%22
But overall we're close enough that tracking this effort here makes sense, IMO.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I'm filing this issue as a continuation of #3338. There was a lot of conceptual discussion in that issue we've moved on from, and I want to discuss concrete steps to merge https://github.com/privacycg/storage-access into HTML here.
There are still a few remaining issues that the SAA editors would like to see resolved before making a PR: https://github.com/privacycg/storage-access/issues?q=is%3Aissue+is%3Aopen+label%3A%22resolve+before+graduation%22
But overall we're close enough that tracking this effort here makes sense, IMO.
The text was updated successfully, but these errors were encountered: