- From: Marcos Caceres <marcosc@apple.com>
- Date: Thu, 15 Dec 2022 14:27:38 +1100
- To: public-webapps <public-webapps@w3.org>
Dear WebApps Members and participants, This is a call for consensus (CFC) to publish the Web Locks API specification as a First Public Working Draft. The latest unpublished draft is at: https://w3c.github.io/web-locks/ The abstract reads: > This document defines a web platform API that allows script to asynchronously acquire a lock over a resource, hold it while work is performed, then release it. While held, no other script in the origin can acquire a lock over the same resource. This allows contexts (windows, workers) within a web application to coordinate the usage of resources. The CFC ends at midnight 31 December, 2022. Please indicate your support for publishing the specification as a W3C First Public Working Draft using either the 👍 or 👎(formal objection) reaction buttons at: https://github.com/w3c/web-locks/issues/112 If you have a formal objection (i.e., you indicate 👎) to its publication, we kindly ask that you raise it before 31 December, 2022. Once approved, it should be published at the following URL: https://www.w3.org/TR/web-locks/ The API is actively being implemented in all major browser engines and, judging by the test results on WPT, already has fairly good interoperability: https://wpt.fyi/results/web-locks Kind regards, Marcos Caceres, Léonie Watson, and Xiaoqian Wu WebApps WG Chairs and W3C Team
Received on Thursday, 15 December 2022 03:28:05 UTC