Re: [w3c/manifest] Drop WebIDL enums (#899)

@annevk, the use case is to take fetch some JSON -> convert into a neutral set of types (e.g., parsed in C++, Rust, JS, whatever) -> process the data into some canonical data structure while performing error handling and assigning defaults/fallback values, then allow the browser to operate on it. 

In my mind, Infra types are ideal for this because they meet the use case of being programming language neutral.  

Just to reiterate the problem: this spec defines things using WebIDL, but no one actually sends the JSON through a WebIDL processor (so the spec doesn't match reality, so would be pointless to add more error handling or pretend this is WebIDL). Chrome processes the JSON using C++, while Gecko does it in JS. 

-- 
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/899#issuecomment-643139218