Re: [whatwg/webidl] Purpose of call-a-user-object’s-operation’s opName parameter (Issue #1282)

Found more context for this: callback interfaces were permitted to have multiple operation members (and attributes) prior to #696, which removed these capabilities because they [weren’t really in use](https://github.com/whatwg/webidl/issues/661). The opName parameter is a relic from before that update.

I also found an [implementation relic of this in Blink](https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/platform/bindings/callback_interface_base.h;l=31;drc=c51240988d5c02b02b137b635e4b92b3e81881ba), where callback interfaces can be `kNotSingleOperation` (but never actually are).



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

Message ID: <whatwg/webidl/issues/1282/1510723729@github.com>

Received on Monday, 17 April 2023 05:27:17 UTC