- From: Philip Jägenstedt <notifications@github.com>
- Date: Fri, 04 Jun 2021 01:41:16 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 4 June 2021 08:43:28 UTC
Thanks @jakearchibald! I think that this sort of thing could be avoided with a faster and more reliable flow of support data from specs and releases into BCD. If there had already been a green row in https://developer.mozilla.org/en-US/docs/Web/API/FetchEvent#browser_compatibility already, something like this might have occurred: - Nobody checked MDN, so the change was made - The spec link in the BCD entry disappeared from [webref](https://github.com/w3c/webref) so this was flagged - Someone reviewing bad spec links in BCD finds their way back here within a week or two and points it out - The relevant implementers are looped in, maybe the change is reverted or maybe it sticks, but *something* happens. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/ServiceWorker/pull/1333#issuecomment-854487218
Received on Friday, 4 June 2021 08:43:28 UTC