- From: Dan Dumont <notifications@github.com>
- Date: Wed, 30 Nov 2022 10:27:41 -0800
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 30 November 2022 18:27:54 UTC
This broke our shipped code. We were using an API that landed in a release of chrome. There needs to be a better way to handle things like this. We have a POSIX filesystem built on top of these APIs (we do not have the problems of asyncify, not using it) that we've shipped to customers, we were relying on the APIs that landed in a release of chrome (after a long time of being roped off, mind you) and this change broke our customers. We now have to release an emergency fix. Please, PLEASE, find other ways to do this in the future. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/772#issuecomment-1332569065 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/772/1332569065@github.com>
Received on Wednesday, 30 November 2022 18:27:54 UTC