David Bruant wrote:
Le 24/06/2012 14:51, Brendan Eich a écrit :
David Bruant wrote:
Instead of adding a new [[instanceofHint]] internal property, maybe the
[[NativeBrand]] could be reused.
+1 on that, which suggests [[NativeBrandMatch]] instead of
[[InstanceofMatch]].
Your proposal is more
On Monday, June 25, 2012 at 4:28 AM, Brendan Eich wrote:
David Bruant wrote:
Le 24/06/2012 14:51, Brendan Eich a écrit :
David Bruant wrote:
Instead of adding a new [[instanceofHint]] internal property, maybe the
[[NativeBrand]] could be reused.
+1 on that, which
On Mon, Jun 25, 2012 at 9:11 AM, David Bruant bruan...@gmail.com wrote:
snip
Firefox is partially built in JavaScript. This code is considered
privileged (by opposition to website JavaScript). More things can be
allowed to this JavaScript code.
In case the DOM is built in pure browser
On Jun 22, 2012, at 11:01 AM, David Bruant wrote:
...
There is a potential security issue. From the wiki [1] (in the case
where the instance is a proxy trapping on instanceof): Security issue:
the handler is given a reference to the function object (the right-hand
side of the instanceof
On Jun 24, 2012, at 5:51 AM, Brendan Eich wrote:
David Bruant wrote:
Instead of adding a new [[instanceofHint]] internal property, maybe the
[[NativeBrand]] could be reused.
+1 on that, which suggests [[NativeBrandMatch]] instead of
[[InstanceofMatch]].
No, the whole point of
Le 25/06/2012 17:36, Allen Wirfs-Brock a écrit :
On Jun 22, 2012, at 11:01 AM, David Bruant wrote:
...
There is a potential security issue. From the wiki [1] (in the case
where the instance is a proxy trapping on instanceof): Security issue:
the handler is given a reference to the function
Le 25/06/2012 17:49, Allen Wirfs-Brock a écrit :
On Jun 24, 2012, at 5:51 AM, Brendan Eich wrote:
David Bruant wrote:
Instead of adding a new [[instanceofHint]] internal property, maybe the
[[NativeBrand]] could be reused.
+1 on that, which suggests [[NativeBrandMatch]] instead of
On Jun 25, 2012, at 11:10 AM, David Bruant wrote:
Le 25/06/2012 17:49, Allen Wirfs-Brock a écrit :
On Jun 24, 2012, at 5:51 AM, Brendan Eich wrote:
David Bruant wrote:
Instead of adding a new [[instanceofHint]] internal property, maybe the
[[NativeBrand]] could be reused.
+1 on that, which
2012/6/25 Allen Wirfs-Brock al...@wirfs-brock.com
On Jun 22, 2012, at 11:01 AM, David Bruant wrote:
...
There is a potential security issue. From the wiki [1] (in the case
where the instance is a proxy trapping on instanceof): Security issue:
the handler is given a reference to the
David Bruant wrote:
Instead of adding a new [[instanceofHint]] internal property, maybe the
[[NativeBrand]] could be reused.
+1 on that, which suggests [[NativeBrandMatch]] instead of
[[InstanceofMatch]].
Your proposal is more general but I think we should extend HasInstance
only very
Le 24/06/2012 14:51, Brendan Eich a écrit :
David Bruant wrote:
Instead of adding a new [[instanceofHint]] internal property, maybe the
[[NativeBrand]] could be reused.
+1 on that, which suggests [[NativeBrandMatch]] instead of
[[InstanceofMatch]].
Your proposal is more general but I think
I'm going to try to move the discussion of this issue to es-discuss via a
separate message as it is mostly about Proxy design. (bcc'ing
public-script-coord)
the start of this subthread is the following which identifies that historically
the [[HasInstance]] extension point has been used (at
On 6/22/12 1:12 PM, Brandon Benvie wrote:
While the issue identified may not be particularly related to multiple
inheritance, the issue in general I think is a looming one in terms of
the goal of being able to self-host the DOM in JS. It seems to be
becoming more and more common for various
On Jun 22, 2012, at 10:12 AM, Brandon Benvie wrote:
While the issue identified may not be particularly related to multiple
inheritance, the issue in general I think is a looming one in terms of the
goal of being able to self-host the DOM in JS. It seems to be becoming more
and more common
Le 22/06/2012 18:13, Allen Wirfs-Brock a écrit :
I'm going to try to move the discussion of this issue to es-discuss
via a separate message as it is mostly about Proxy design. (bcc'ing
public-script-coord)
the start of this subthread is the following which identifies that
historically the
Allen Wirfs-Brock wrote:
I agree, I don't see that it presents any technical hurdles.
Agreed.
The DOM is alas built from nominal types, so many people believe (x
instaceof I) for some WebIDL-declared interface I, even if that I came
from another window or frame, should just work.
Of
While the issue identified may not be particularly related to multiple
inheritance, the issue in general I think is a looming one in terms of the
goal of being able to self-host the DOM in JS. It seems to be becoming more
and more common for various kinds of partial
17 matches
Mail list logo
