- From: Matt Giuca <notifications@github.com>
- Date: Sun, 19 Jan 2020 18:02:24 -0800
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 20 January 2020 02:02:27 UTC
Hi Marcos, I've discussed the issue internally with various colleagues on Chrome. @slightlyoff suggested as a compromise position that BeforeInstallPrompt be removed from the normative part of the spec, and placed into a "non-normative annex" at the bottom. He cited ECMAScript which has done this (e.g. https://www.ecma-international.org/ecma-262/5.1/#sec-B). This annex would basically say "this is not part of the standard, and you do not need to implement it to comply with the standard, **but**, if you do implement it, you might want to implement this API rather than designing your own." That would allow browsers that do implement it to remain in agreement (without having to go off and find a side document). Basically what @aarongustafson suggested earlier but it wouldn't be a vague note, it would be a complete non-normative specification. What do you think of that counter-proposal? -- 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-576077495
Received on Monday, 20 January 2020 02:02:27 UTC