Re: [w3c/manifest] Use WebIDL to describe the manifest data structure (#611) from Marcos Cáceres on 2018-12-12 (public-webapps-github@w3.org from December 2018)

From: Marcos Cáceres <notifications@github.com>
Date: Tue, 11 Dec 2018 23:28:02 -0800
To: w3c/manifest <manifest@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/manifest/issues/611/446488941@github.com>

I'm still unsure what the problem is with just having a single property extraction algorithm as per 
https://github.com/mozilla/gecko-dev/blob/master/dom/manifest/ValueExtractor.jsm#L34? And the example I gave. They object definitions are concise and get the job done in the same way that that defining an extended attribute would. 

As @annevk mentioned, if we add things like [StrictString] and [CatchTypeError], they are going to leak into everyday WebIDL interfaces. I really don't think we want a special set of WebIDL things for a JSON format VS having a thing just Web APIs. 

-- 
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/611#issuecomment-446488941

Received on Wednesday, 12 December 2018 07:28:23 UTC