Re: [heycam/webidl] Update method creation for operations (#155)

> +                            not the appropriate global object.)
> +
> +                            <!-- https://www.w3.org/Bugs/Public/show_bug.cgi?id=18547#c9 -->
> +                          </li>
> +
> +                          <li>Otherwise, set <var>O</var> to the <span class='esvalue'>this</span>
> +                          value.</li>
> +
> +                          <li>If <var>O</var> is a <a class='dfnref'
> +                          href='#dfn-platform-object'>platform object</a>, then <a class='dfnref'
> +                          href='#dfn-perform-a-security-check'>perform a security check</a>,
> +                          passing <var>O</var>, <var>realm</var>, <var>id</var>, and "method".</li>
> +
> +                          <li>If <var>O</var> is not a <a class='dfnref'
> +                          href='#dfn-platform-object'>platform object</a> that implements the
> +                          interface <var>target</var>, <a href='#ecmascript-throw' class='dfnref

This is not quite right, depending on what it means to "implement" an interface.  The current spec text is careful to ensure that `I` is an actual interface, not a mixin (except for the weirdness around globals, wheere I don't understand what the current spec text is doing and why).  I think we should fix the caller of this algorithm to pass in the "interface whose interface prototype object (or interface object, for a static operation) this property corresponding to the operation appears on" to preserve the current semantics.  At _that_ point calling it `target` would make sense, actually.

-- 
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/155/files/5f3f6f66bb2d8cfbf1c7197e64f2b54f9cdd2845#r76880809