- From: Domenic Denicola <notifications@github.com>
- Date: Wed, 31 Aug 2016 15:59:29 -0700
- To: heycam/webidl <webidl@noreply.github.com>
- Message-ID: <heycam/webidl/pull/155/r77088945@github.com>
> + 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 Also I think that wording actually doesn't work at all. There is no "the" interface whose interface prototype object is `Navigator.prototype`. Navigator, NavigatorID, and NavigatorConcurrentHardware are all interfaces whose interface prototype object is `Navigator.prototype`. Otherwise the previous step, which says "Otherwise, the property exists solely on the interface’s interface prototype object" would not work at all for NavigatorID. Maybe the solution here is to use a vague phrase like "the interface (or the interface it's being mixed in to, if the interface is actually a mixin)" and have a bug to define this correctly later? If we do that we probably won't fix this until we actually separate out mixins, but that's probably OK given that the current spec seems broken. -- 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#r77088945
Received on Wednesday, 31 August 2016 23:00:04 UTC