- From: cynthia <notifications@github.com>
- Date: Tue, 01 Aug 2023 00:43:30 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 1 August 2023 07:43:36 UTC
We briefly discussed this during our F2F, overall - this looks good. **However**, we couldn't see how the lock is expected to behave when the document becomes not fully active, or if the rug is pulled from underneath (e.g. crash). Effectively, there doesn't seem to be a mechanism in place for recovery; or getting out of a stale lock state. Could you elaborate on what you have in mind here and possibly add that to the explainer? Also, the other implementer signal is a pointer to a long thread, where we can't really identify who is from which implementer. It would be helpful if there was at least a pointer to the actual comment from each implementer. (Ideally we'd want to see a standards position.) -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/845#issuecomment-1659748044 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/845/1659748044@github.com>
Received on Tuesday, 1 August 2023 07:43:36 UTC