The Web Locks documentation explains that it works across tabs, i.e. separate processes: ”[…] allows a web app running in multiple tabs or workers to coordinat

The Web Locks documentation explains that it works across tabs, i.e. separate processes: ”[…] allows a web app running in multiple tabs or workers to coordinate work and the use of resources” A locking API is much more natural and less error-prone for this use case than using shared memory and atomics.