On Jul 25, 3:48=A0pm, "Aaron Gray" <ang.use...@[EMAIL PROTECTED]
> wrote:
> "Thomas 'PointedEars' Lahn" <PointedE...@[EMAIL PROTECTED]
> wrote in
messagenews:488=
A5161.4090004@[EMAIL PROTECTED]
>
>
> > therefore the equals operation does not need to work like with native
> > objects. =A0(Nevertheless, no hard proof has been provided yet of an
> > implementation showing different behavior.)
>
How about the window object in MSIE?
<script>
window.foo =3D function() { alert([this.do***ent =3D=3D window.do***ent,
this =3D=3D window]); };
foo();
</script>
IE: alert "true, false"
All other browsers would alert "true, true"
Though it is likely that the unexpected result is caused by the
identity of "window" and "this" being different (a "cloned" window)
and probably not bug of the equals operator.
> Anyway I have part read 262 twice, its not easy digestable,
That is true.
Other specifications that are useful are the DOM specs, CSS2.1, and
HTML 4.01
> have been
> meaning to put in a full time reading at some point :)
>
It's not a great sit-down read-through.
Some parts that might seem more relevant and easier to digest:
Execution COntexts, Scope Chain and identifier Resolution, the built
in types (Array, et c), and the operators parts are useful and not as
hard t understand.
The reference for things like "Array.prototype.un****ft" method are
useful.
Garrett
> Cheers Thomas,
>
> Aaron
|
