- From: Domenic Denicola <notifications@github.com>
- Date: Wed, 18 Jan 2023 15:59:52 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 19 January 2023 00:00:06 UTC
My current thinking is web platform specs should not do any work in this area until there is parity between async and sync dispose. Having only a random subset of web objects (those with sync disposal) be usable with this new syntax is something I'd like to avoid on the web platform. And having to push the spec/implementation/tests ecosystem through an adoption curve twice, once for sync and once for async, is not something I think the community should spend time on. (Certainly it's not something I'll advise Chromium spec and implementation engineers against spending time on.) -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/discussions/800#discussioncomment-4722727 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/repo-discussions/800/comments/4722727@github.com>
Received on Thursday, 19 January 2023 00:00:06 UTC