That's basically what the Global Scope Polluter does. That's certainly how I
plan to implement it in Gecko in the WebIDL bindings:
Window.prototype.__proto__ will be a proxy which will do all the weird stuff
the GSP has to do.
In FF 14, I’m getting the following results (if there is an
Travis Leithead wrote:
From: Cameron McCormack [mailto:c...@mcc.id.au]
Brendan Eich:
As noted, they started out that way 17 years ago. I think WebIDL and
interface-based method definition made onload, e.g., predefined on
window objects, or more recently on Window.prototype. Was this useful?
Recently, Allen produced a strawman proposal[0][1] for the object define
properties operator, which was designed to provide syntax that
differentiated semantics of define vs. assign. Towards the end of the
thread, IIRC, Brendan suggested some new Object functions: Object.define()
and
Travis Leithead wrote:
From: Boris Zbarsky [mailto:bzbar...@mit.edu]
On 8/12/12 5:29 PM, Brendan Eich wrote:
Boris Zbarsky wrote:
Note that data in
http://lists.w3.org/Archives/Public/public-script-coord/2012JanMar/00
33.html suggests that IE also implements the erratum to 5.1 we were
talking
Rick Waldron wrote:
As a result, I re-drafted Object.assign based on the real-world use
cases, but specifically does not attempt nested object property
assignment recursion. At this point I still believe that the deep
nested assignement case is strong enough to consider, but I'm not sure
how
On Wed, Aug 15, 2012 at 5:30 PM, Brendan Eich bren...@mozilla.org wrote:
Rick Waldron wrote:
As a result, I re-drafted Object.assign based on the real-world use
cases, but specifically does not attempt nested object property assignment
recursion. At this point I still believe that the deep
Le 15/08/2012 21:42, Rick Waldron a écrit :
Recently, Allen produced a strawman proposal[0][1] for the object
define properties operator, which was designed to provide syntax that
differentiated semantics of define vs. assign. Towards the end of the
thread, IIRC, Brendan suggested some new
This topic has probably been beaten to death years before I was even aware
of es-discuss but it continues to get mentioned occasionally as a point of
pain so I thought I'd see if I couldn't attempt to hatch a conversation and
maybe understand the design concerns better than I likely do now.
Le 16/08/2012 00:35, Rick Waldron a écrit :
On Wed, Aug 15, 2012 at 6:02 PM, Erik Reppen erik.rep...@gmail.com
mailto:erik.rep...@gmail.com wrote:
Is consistent type return a heuristic carried over from more
strictly-typed paradigms or would it murder performance of the
Le 14/08/2012 04:16, Allen Wirfs-Brock a écrit :
check out the current ES66 spec. draft. Based upon discussions at the
March TC39 meeting hypot2 was eliminated and an optional third
argument as added to hypot.
Quoting relevant part of the March meeting notes [1]:
Discussion of hypot, hypot2.
For those puzzled by the subject line: It's a reference to a test in the
growing conformance test suite for the ECMAScript Internationalization API,
currently available here:
http://lindenbergsoftware.com/ecmascript/test262/tests1013.patch
For this specific test, an implementation could simply
On Aug 15, 2012, at 5:09 PM, David Bruant wrote:
Le 14/08/2012 04:16, Allen Wirfs-Brock a écrit :
check out the current ES66 spec. draft. Based upon discussions at the
March TC39 meeting hypot2 was eliminated and an optional third
argument as added to hypot.
Quoting relevant part of the
On Aug 15, 2012, at 15:35 , Rick Waldron wrote:
On Wed, Aug 15, 2012 at 6:02 PM, Erik Reppen erik.rep...@gmail.com wrote:
* 'wombat'.charAt(20); //returns an empty string, but that's a concrete
value whereas 'wombat'[20] returns undefined
For the same reason indexOf always returns a
13 matches
Mail list logo
