Re: [heycam/webidl] Stop claiming callback interfaces are interfaces (#705)

domenic approved this pull request.

I admit not being able to review every line, but overall this change makes sense, and I did my best to read through and try to spot any problem areas.

> @@ -5832,6 +5840,31 @@ The [=type name=] of an interface type
 is the [=identifier=] of the interface.
 
 
+<h4 id="idl-callback-interface" dfn>Callback interface types</h4>
+
+An [=identifier=] that identifies a [=callback interface=] is used to refer to a type that
+corresponds to the set of all possible non-null references to objects.
+
+An IDL value of the interface type is represented by a tuple of an object reference and a
+<dfn id="dfn-callback-context" export>callback context</dfn>.
+The [=callback context=] is a language binding specific value, and is used to store information
+about the execution context at the time the language binding specific object reference is
+converted to an IDL value.
+
+Note: For ECMAScript objects, the [=callback context=] is used to hold a reference to the
+[=incumbent settings object=] at the time the Object value is converted to an IDL callback
+interface type value. See [[#es-interface]]./XXX

/XXX?

> @@ -1409,6 +1361,70 @@ you can extend the {{WindowOrWorkerGlobalScope}} [=interface mixin=] using a [=p
     };
 </pre>
 
+
+<h3 id="idl-callback-interfaces">Callback interfaces</h3>
+
+A <dfn id="dfn-callback-interface" export>callback interface</dfn> is a [=definition=] matching
+<emu-t>callback</emu-t> <emu-t>interface</emu-t> <emu-nt><a href="#prod-InterfaceRest">InterfaceRest</a></emu-nt>.
+It can be implemented by any object, as described in [[#idl-objects]].

Can we note somewhere around here (i.e. early) that the name "callback interfaces" is a legacy holdover?

-- 
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/pull/705#pullrequestreview-222839887