Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.javascript > #28673

Re: problem same element objetc

Newsgroups comp.lang.javascript
Subject Re: problem same element objetc
From "Evertjan." <exxjxw.hannivoort@inter.nl.net>
References <410a3c99-009d-45cb-aa85-119c0bb2e213@googlegroups.com> <7072940f-53ff-4545-8919-1e928666b8d7@googlegroups.com>
Date 2015-09-10 21:04 +0200
Message-ID <XnsA511D6719A10eejj99@194.109.6.166> (permalink)

Show all headers | View raw


Sam Desborough <sam.desborough@gmail.com> wrote on 10 Sep 2015 in
comp.lang.javascript: 

> On Thursday, September 10, 2015 at 3:50:56 PM UTC+1, WALID BELRHALMIA
> wrote: 
>> i have a question when we do var e= document.getElemtById("foo")  i get
>  the object>Node>element  that it hase id="foo"  . But when i do
>  e===document.getElemtById("foo") i get true it's the same object it
>  return always the some object can someone explain me how that work 
> 
> It's the same as saying 1 === 1.

That might be true in a steady state.

However, things could have changed between the assignment of e
and the subsequent comparison in a way that the id has moved 
[was signed] to another node.

> saying 1 === 1

That English has "one and another one" goes without saying.

Ah well, let's stipulate you are right, Sam.

-- 
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

Back to comp.lang.javascript | Previous | Next — Previous in thread | Find similar | Unroll thread


Thread

problem same element objetc WALID BELRHALMIA <wbelrhalmia@gmail.com> - 2015-09-10 07:50 -0700
  Re: problem same element objetc "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2015-09-10 17:12 +0200
  Re: problem same element objetc Sam Desborough <sam.desborough@gmail.com> - 2015-09-10 11:43 -0700
    Re: problem same element objetc "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2015-09-10 21:04 +0200

csiph-web