- From: Darien Maillet Valentine <notifications@github.com>
- Date: Fri, 17 Mar 2023 13:33:38 -0700
- To: whatwg/webidl <webidl@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 17 March 2023 20:33:51 UTC
Callback interfaces are required to have one-and-only-one regular operation\*, which has a particular name. However [call a user object’s operation](https://webidl.spec.whatwg.org/#call-a-user-objects-operation) requires an `opName` parameter. This permits the algorithm to be invoked with a different name than the operation name that was given in the callback interface type that `value` is an instance of. The only usages of the algorithm I could find are in the DOM spec, which always passes an `opName` that does align with the name of the CBI’s operation member. Is there any reason for this parameter to exist given it’s a static part of the type definition? It seems likely that it’s unintentional that it permits passing a different name. _\* Which isn’t really an operation in the same sense that word is used elsewhere in the spec; it just uses the same syntax._ -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/webidl/issues/1282 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/webidl/issues/1282@github.com>
Received on Friday, 17 March 2023 20:33:51 UTC