[heycam/webidl] Unexplained restrictions in operation bindings section (#511)

The [first sentence of the Operation bindings section](https://heycam.github.io/webidl/#es-operations) reads (empahsis mine):

> For each unique identifier of an exposed operation defined on the interface, there must exist a corresponding property, *unless the effective overload set for that identifier and operation and with an argument count of 0 has no entries.*

I'm unsure what the intent of the emphasized part of that sentence is. Are there existing APIs that end-up not being exposed because of this clause, and if so, why should they?

Will document this via a note so future me doesn't get confused again.

Tagging @heycam, @bzbarsky, and @domenic. Thanks in advance for your help.


-- 
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/511