Re: [heycam/webidl] Need pattern for feature detecting dictionary members (#107)

I don't understand why we're squeamish about exposing dictionary names to the web.  The names are already required to be unique in the WebIDL ecosystem, as they live in the same namespace as interfaces.  The names are also usually quite long and weird, so collision chance is low.

I'm strongly against something that requires spec authors to affirmatively annotate their dictionary-taking APIs to make them dict-member-detectable, because that just means that most dict-taking APIs won't have it, and authors will have to remember yet another detail of the API (whether or not it exposes that feature-detection) before they try to use it, and there'll be browser differences in whether it's supported or not in a particular browser/version...  All of this is bad and unnecessary when we can just somehow globally expose all dictionaries.

I don't care if we do it with a single global function like `IDLDictSupports("dictName", "memberName")` instead of adding a bunch of dictionary names to the global, I just care that it works for everything automatically.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/heycam/webidl/issues/107#issuecomment-304160508