- From: Ayumi Hamasaki <notifications@github.com>
- Date: Fri, 24 Aug 2018 17:28:34 +0000 (UTC)
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 24 August 2018 17:28:57 UTC
See the following two webpage examples: In Google Developers Page found here: https://developer.chrome.com/apps/manifest In FireFox MDN Web Docs found here: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Browser_compatibility_for_manifest.json As you can see there are many properties not mentioned in the Spec's. Some questions jump into my mind to ask: 1. Is it safe to use Properties not mentioned in the Spec? 1.a) Can Browsers Still Read the Data in the Manifest File if the Property is not Supported (yet). 1.b) Would w3c add something to the spec to stop that, or block it or something else related in that respect. 2. Will these Properties be added to the Spec at a later date - I do understand its still in Draft. However, there are so many good Properties out there that would seem to have some good benefit to be added. These are my main questions but I am sure people would have lots more questions to this! * Personally I would love to see many of these new properties in the Manifest File. Things like `author`, `description`, `developer` etc. Would be nice to move `humans.txt` into the manifest file. -- 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/issues/711
Received on Friday, 24 August 2018 17:28:57 UTC