Skip to content
New issue

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

Move Web Locks to Normative Specifications section #73

Closed
saschanaz opened this issue Aug 18, 2021 · 6 comments
Closed

Move Web Locks to Normative Specifications section #73

saschanaz opened this issue Aug 18, 2021 · 6 comments

Comments

@saschanaz
Copy link
Member

@saschanaz saschanaz commented Aug 18, 2021

(Following #70)

Since Google already shipped it and Mozilla is now prototyping it (thread), it's probably time to consider taking it as a normative spec.

cc @tantek

@marcoscaceres
Copy link
Member

@marcoscaceres marcoscaceres commented Aug 22, 2021

Absolutely. It’s already in our updated as something we plan to adopt:

<a href="https://github.com/WICG/web-locks/">Web Locks API</a>

In the meantime, please keep working on the spec and make sure it’s in the best shape possible for us to bring over to the W3C.

@annevk
Copy link
Member

@annevk annevk commented Oct 19, 2021

Can someone clarify what is holding this back?

@marcoscaceres
Copy link
Member

@marcoscaceres marcoscaceres commented Oct 19, 2021

Nothing. I just need to send a pull request to the draft charter. There were some other formal objections that delayed the charter renewal, but not related to this.

@marcoscaceres
Copy link
Member

@marcoscaceres marcoscaceres commented Oct 21, 2021

PR #81

@marcoscaceres
Copy link
Member

@marcoscaceres marcoscaceres commented Oct 21, 2021

Sent also WICG/web-locks#84 in preparation to move it over.

@annevk
Copy link
Member

@annevk annevk commented Oct 21, 2021

Thanks @marcoscaceres!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

3 participants