- From: Ryosuke Niwa <notifications@github.com>
- Date: Sun, 15 Dec 2019 20:33:41 -0800
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 16 December 2019 04:33:44 UTC
> Regardless, if this is taken out of the spec, I think it's unlikely it'll be removed from Chromium. There is too much developer demand for this feature, and we think we've found a good balance between developer demand and being respectful of the user. We would likely take the text of this API and move it into its own spec (maybe in WICG). FWIW, I don’t think moving to WICG is appropriate. WICG is a place for people to *incubate* ideas, not a place to hoard all the ideas that have failed / rejected (for the lack of better words) elsewhere. In the case of a single vendor browser feature like this, producing a technical note or adding an obsolete section in the spec is what we’d usually do. -- 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/manifest/pull/836#issuecomment-565900865
Received on Monday, 16 December 2019 04:33:44 UTC