> but at the same time it's a feature defined as a finalized spec in the Web incubator. At the dame time both Firefox and Safari consider this feature harmful

> but at the same time it's a feature defined as a finalized spec in the Web incubator. At the dame time both Firefox and Safari consider this feature harmful and will not implement it. Just because you rammed it through standards bodies doesn't make it standard, or good. And, unfortunately, you've co-opted web.dev to be a full-on Chrome propaganda machine. Additionally, the status of this "finalized spec" is, quote, "Draft Community Group Report". It's nowhere near to being a) finalized and b) standardized. The "finalized spec" literally has this in its description: "It is not a W3C Standard nor is it on the W3C Standards Track." > For example, File System Access API 1. Is anyone talking about this API here? No. Only you, trying to pull conversation away from WebUSB 2. Filesystem API suffers from the same thing: it's a "standard", and now your team is busy pushing three more file standards