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

Groups > comp.lang.javascript > #18258 > unrolled thread

FAQ Topic - Why does my code fail to access an element? (2013-01-26)

Back to article view | Back to comp.lang.javascript

Contents

  FAQ Topic - Why does my code fail to access an element? (2013-01-26) "FAQ server" <javascript@dotinternet.be> - 2013-01-26 00:00 +0000
    Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) Dr J R Stockton <reply1300@merlyn.demon.co.uk.invalid> - 2013-01-27 19:49 +0000
      Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2013-01-28 01:32 +0100
        Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) Richard Yates <richard@yatesguitar.com> - 2013-01-27 19:16 -0800
          Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2013-01-28 11:58 +0100
        Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) Dr J R Stockton <reply1300@merlyn.demon.co.uk.invalid> - 2013-01-29 23:12 +0000
          Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) Gene Wirchenko <genew@telus.net> - 2013-01-29 16:45 -0800
          Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) Andrew Poulos <ap_prog@hotmail.com> - 2013-01-30 14:38 +1100
            Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2013-01-30 09:52 +0100
          Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2013-01-30 09:31 +0100
      Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) Andrew Poulos <ap_prog@hotmail.com> - 2013-01-28 21:55 +1100
        Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2013-01-28 16:16 +0100
          Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) Andrew Poulos <ap_prog@hotmail.com> - 2013-01-29 08:35 +1100
            Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-01-28 23:40 +0100
              Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2013-01-29 00:21 +0100
                Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2013-01-29 00:53 +0100
                  Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2013-01-29 21:24 +0100
                    Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) John G Harris <niam@jghnorth.org.uk.invalid> - 2013-01-30 14:31 +0000
                      Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2013-01-30 20:22 +0100
                        Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) John G Harris <niam@jghnorth.org.uk.invalid> - 2013-01-31 10:55 +0000
                          Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2013-01-31 22:42 +0100
                            Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) John G Harris <niam@jghnorth.org.uk.invalid> - 2013-02-01 10:55 +0000
                              Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2013-02-01 16:03 +0100
                    Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) Dr J R Stockton <reply1300@merlyn.demon.co.uk.invalid> - 2013-01-30 15:09 +0000
            Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2013-01-29 00:03 +0100
      Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) John G Harris <niam@jghnorth.org.invalid> - 2013-01-29 10:10 +0000
        Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) Dr J R Stockton <reply1300@merlyn.demon.co.uk.invalid> - 2013-01-30 15:14 +0000
          Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) John G Harris <niam@jghnorth.org.uk.invalid> - 2013-01-31 10:50 +0000
            Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) Dr J R Stockton <reply1300@merlyn.demon.co.uk.invalid> - 2013-02-01 23:29 +0000
              Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) John G Harris <niam@jghnorth.org.uk.invalid> - 2013-02-02 11:10 +0000
                Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) Dr J R Stockton <reply1300@merlyn.demon.co.uk.invalid> - 2013-02-03 19:39 +0000
                  Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) Christoph Becker <cmbecker69@gmx.de> - 2013-02-04 01:56 +0100
                    Re: FAQ Topic - Why does my code fail to access an element? (2013-01-26) Dr J R Stockton <reply1300@merlyn.demon.co.uk.invalid> - 2013-02-06 16:08 +0000

Page 2 of 2 — ← Prev page 1 [2]

#18306

John G Harris wrote on 31 jan 2013 in comp.lang.javascript:

> In message <XnsA158CF4994E69eejj99@194.109.133.133>, Evertjan. wrote:
> 
>   <snip>
>>The standard you seem to quote is about html definitions of elements of
>>the script, not about the parsing of such script or how it should appear
>>in the dom, I am sure.
>   <snip>
> 
> "script" ?

Yes, indeed.

> I'm talking about the HTML text: 

The HTML-string, [I hope you mean that],
that can be stored and retrieved in a file,
is a text-string in the form of a script, 
as it describes to the parsing engine what te do. 

However it is not a file that reaches the browser,
just a STREAM containing html-script.

Often there never existed a file with that html,
for example in a particular asp-file where the serverside code 
describes to the serverside parsing engine how to construct
the html-stream without any intermediate storage-file.

> the .html file.

HTML can contained in a file with any extension.

Some popular ones are:

.html [indeed]
.htm [ms]
.hta [ms]
.asp [ms]
.aspx [ms]
.php
.cnn [cnn.com does this]

Often they contain a mixture of serverside code and html,
perhaps also other script than clientside html, 
like javascript, css, vbscript.

However you might want to name it

.whateversillyme

As long as you instruct the server to send the html to the browser 
with a header instructing that browser to parse the STREAM as html,
the browser will parse that STREAM as an HTML-SCRIPT.

IIS, the serverside engine of Windows, can also be instructed to treat an 
.html-file as an asp source for the resulting stream, where that 
particular .html-file contains no html at al, but the resulting stream 
does.


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

[toc] | [prev] | [next] | [standalone]

#18308

In message <XnsA159E6EE6D95Ceejj99@194.109.133.133>, Evertjan. wrote:
>John G Harris wrote on 31 jan 2013 in comp.lang.javascript:
>
>> In message <XnsA158CF4994E69eejj99@194.109.133.133>, Evertjan. wrote:
>>
>>   <snip>
>>>The standard you seem to quote is about html definitions of elements of
>>>the script, not about the parsing of such script or how it should appear
>>>in the dom, I am sure.
>>   <snip>
>>
>> "script" ?
>
>Yes, indeed.
>
>> I'm talking about the HTML text:
>
>The HTML-string, [I hope you mean that],
>that can be stored and retrieved in a file,
>is a text-string in the form of a script,
>as it describes to the parsing engine what te do.

HTML is a mark-up language for describing documents so I would not use
the word 'script'. You can use the word if you like, but you mustn't
complain about people who don't.

And parsing is not restricted to scripting languages.


>However it is not a file that reaches the browser,
>just a STREAM containing html-script.
  <snip>

I'm well aware that the HTML text can come from a variety of sources,
but I'm using 'file' for what arrives. For me, a file does not have to
have an image in a secondary storage device. (The HTTP specification
calls it an entity-body, by the way).


  John
-- 
John Harris

[toc] | [prev] | [next] | [standalone]

#18309

John G Harris wrote on 01 feb 2013 in comp.lang.javascript:

> HTML is a mark-up language for describing documents so I would not use
> the word 'script'. You can use the word if you like, but you mustn't
> complain about people who don't.

I certainly did not. I never complain.

> And parsing is not restricted to scripting languages.

I did not say so. Scripts are not restricted to scripting languages


However parsing of a script to get the commands and the data, wether for 
compiling [making an intermediate that can be used by it self and 
distributed] or interpreting [immediate execution or making an 
intermediate that is used immediately] is parsing.

>>However it is not a file that reaches the browser,
>>just a STREAM containing html-script.
>   <snip>
> 
> I'm well aware that the HTML text can come from a variety of sources,
> but I'm using 'file' for what arrives.

Methinks that is a very strange way to use the concept "file".

Sometimes I do this:

<img src='myPictures.asp?John'> 

or even:

<img src='nextPicture.asp'> 

to get a picture stream that is only available to people logged in, 
and/or to count the number of downloads and/or to register the IP of the 
user. 'nextPicture.asp' will give the next picture stream on each call, 
counting application- or session-wide.

What name would you give the stream that you call a file here?

In it's simplistic vbs form:
<%
   Set objStream = Server.CreateObject("ADODB.Stream")
   objStream.Open

   objStream.Type = 1
   objStream.LoadFromFile strFilePath

   Response.AddHeader "Content-Type", "image/JPEG"

   do while Not objStream.EOS
      Response.BinaryWrite objStream.Read 4096*64
      Response.Flush
      Response.Clear
   loop
	
   objStream.Close
   Set objStream = Nothing
%>


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

[toc] | [prev] | [next] | [standalone]

#18302

In comp.lang.javascript message <XnsA157D9C879872eejj99@194.109.133.133>
, Tue, 29 Jan 2013 21:24:32, Evertjan. <exxjxw.hannivoort@inter.nl.net>
posted:

>Thomas 'PointedEars' Lahn wrote on 29 jan 2013 in comp.lang.javascript:
>
>>> Element-object van easily be called "elements", when they are part of
>>> the document.
>>>
>>> Otherwise you should not say "document", but "document-object".
>>>
>>> Elements are not parsed,
>>
>> Utter nonsense, all of the above.
>
>So why is it right for you to call the document-object just document,
>and not for me to call an element-object not an element?
>
>
>repeat>> Elements are not parsed,
>
>So you maintain elements are parsed?
>
>Please explain where and how with a logical responce,
>and not with borish exclamations like "utter nonsense".

You must be thinking of either "boring" or "boorish".  Please try not to
confuse two different English words, especially when either would be
appropriate for the context.  That does not apply to your ingenious
mutation of "response", however.

<http://www.merlyn.demon.co.uk/quotings.htm#AWY>.

-- 
 (c) John Stockton, nr London, UK.  For Mail, see Home Page.  Turnpike, WinXP.
 Web  <http://www.merlyn.demon.co.uk/> - FAQ-type topics, acronyms, and links.
 Command-prompt MiniTrue is useful for viewing/searching/altering files. Free,
 DOS/Win/UNIX now 2.0.6; see <URL:http://www.merlyn.demon.co.uk/pc-links.htm>.

[toc] | [prev] | [next] | [standalone]

#18286

Andrew Poulos wrote on 28 jan 2013 in comp.lang.javascript:

> On 29/01/2013 2:16 AM, Evertjan. wrote:
>> Andrew Poulos wrote on 28 jan 2013 in comp.lang.javascript:
>>
>>> On 28/01/2013 6:49 AM, Dr J R Stockton wrote:
>>>> In comp.lang.javascript message
>>>> <51031c8a$0$289$14726298@news.sunsite.dk 
>>>>> , Sat, 26 Jan 2013 00:00:03, FAQ server
>>>>> <javascript@dotinternet.be> 
>>>> posted:
>>>>
>>>>>
>>>>> An element can only be accessed after it exists in the document.
>>>>>
>>>>
>>>> False.  An element cannot be accessed after it exists; it can only
>>>> be accessed while it exists.
>>>
>>> And how have you defined "exists". Surely an element "exists" in the
>>> HTML even if the browser has not yet parsed the relevant HTML?
>>
>> HTML is just a string of text, the only elements being character
>> numbers. 
> 
> Are saying that when some agent parses some HTML then and only then
> has the document come into existence? Hence an element can't exist
> until the document does?

Quite so, if you define document as part of the DOM-tree.

[However you could define document as a piece of parchment, 
or a .docx or .xlsx file or a driving licence on a plastic card.]

And "exist": A document's element, in the sense of accessability by 
clientside code, surely must be defined with the above DOM-tree 
definition. 

Some elements are part of the document in one browser, but not in another.
For example an 'empty text' element, where the source-html is the same. 
That is why sometimes the count of a childNodes-collection differs to 
anyones amazement.

"..ML":

A "mark-up language" just defines source-text, that contains simple text 
AND markup, specially defined text-parts that are not to be displayed but 
serve as suggestions of how to visualize this text in the widest sense. 
Widest, because it can suggest dynamic views, sounds, smells, etc.
Suggestions, because the browser engine has and must have much freedom of 
interpretation. The different parts are called elements of the build 
document.

"HT..":

"hypertext" just defines the ability to make externally-pointing links in 
the document, you could perhaps call an interactive dynamic property.


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

[toc] | [prev] | [next] | [standalone]

#18291

In message <q7VcV3KhTYBRFwQv@invalid.uk.co.demon.merlyn.invalid>, Dr J R
Stockton wrote:
>In comp.lang.javascript message <51031c8a$0$289$14726298@news.sunsite.dk
>>, Sat, 26 Jan 2013 00:00:03, FAQ server <javascript@dotinternet.be>
>posted:
>
>>
>>An element can only be accessed after it exists in the document.
>>
>
>False.  An element cannot be accessed after it exists; it can only be
>accessed while it exists.

<FAQENTRY>

  If anyone else is worried by this then better wording would be :

An element can only be accessed after it comes into existence in the
document.

  Or for the really picky :

The DOM object representing an HTML element can only be accessed after
it comes into existence in the document object.

  John
-- 
John Harris

[toc] | [prev] | [next] | [standalone]

#18303

In comp.lang.javascript message <6HBzbHF9$5BRFwBz@J.A830F0FF37FB96852AD0
8924D9443D28E23ED5CD>, Tue, 29 Jan 2013 10:10:05, John G Harris
<niam@jghnorth.org.invalid> posted:

>In message <q7VcV3KhTYBRFwQv@invalid.uk.co.demon.merlyn.invalid>, Dr J R
>Stockton wrote:
>>In comp.lang.javascript message <51031c8a$0$289$14726298@news.sunsite.dk
>>>, Sat, 26 Jan 2013 00:00:03, FAQ server <javascript@dotinternet.be>
>>posted:
>>
>>>
>>>An element can only be accessed after it exists in the document.
>>>
>>
>>False.  An element cannot be accessed after it exists; it can only be
>>accessed while it exists.
>
><FAQENTRY>
>
>  If anyone else is worried by this then better wording would be :
>
>An element can only be accessed after it comes into existence in the
>document.
>
>  Or for the really picky :
>
>The DOM object representing an HTML element can only be accessed after
>it comes into existence in the document object.


Certainly not.  Those are accurate only if read carefully, and it easy
enough to write a version lacking that fault, and another :

"An element can be accessed only while it exists in a document."


-- 
 (c) John Stockton, Surrey, UK.  ¬@merlyn.demon.co.uk   Turnpike v6.05   MIME.
   Web  <http://www.merlyn.demon.co.uk/> - FAQish topics, acronyms, & links.
 Proper <= 4-line sig. separator as above, a line exactly "-- " (SonOfRFC1036)
 Do not Mail News to me. Before a reply, quote with ">" or "> " (SonOfRFC1036)

[toc] | [prev] | [next] | [standalone]

#18304

In message <yjcaDVEIjTCRFw64@invalid.uk.co.demon.merlyn.invalid>, Dr J R 
Stockton wrote:

   <snip>
>"An element can be accessed only while it exists in a document."

Then this has to be followed by a reminder that the element object might 
not exist yet when the failing code is executed. That's the whole point 
of the FAQ entry.

The FAQ entry is not about what happens when an element object is 
removed from the DOM tree.

   John
-- 
John Harris

[toc] | [prev] | [next] | [standalone]

#18310

In comp.lang.javascript message <jrYmgXE+xkCRFwIa@J.A830F0FF37FB96852AD0
8924D9443D28E23ED5CD>, Thu, 31 Jan 2013 10:50:38, John G Harris
<niam@jghnorth.org.uk.invalid> posted:

>In message <yjcaDVEIjTCRFw64@invalid.uk.co.demon.merlyn.invalid>, Dr J
>R Stockton wrote:
>
>  <snip>
>>"An element can be accessed only while it exists in a document."
>
>Then this has to be followed by a reminder that the element object
>might not exist yet when the failing code is executed. That's the whole
>point of the FAQ entry.

That should be obvious, but can be covered by something like "... in a
document, as part of the DOM tree.".  Except, of course, for the fact
that it would then be incorrect.

        "An element can be accessed only while it exists."

The "in a document" is probably intended to mean "in the DOM tree"
(which is sufficient but not necessary), and might by the intended
readership be taken as meaning "in the HTML" or "in
document.body.innerHTML" or similar.

 "An element can be accessed only while it and a reference to it exist."

>The FAQ entry is not about what happens when an element object is
>removed from the DOM tree.


That was the original intention.  But the original intention is
irrelevant; it is the Subject which defines the question.

Imagine, for example

<div ID=A>xxx<span ID=B>yyy</span>zzz</span>

<script>
  RA = document.getElementById("A")
  RB = document.getElementById("B")
</script>

It is easy to write to A and to B.

After   RA.innerHTML = "---"   it should be clear enough that B cannot
be visibly written to, as it no longer visibly exists.  But a reference
to it exists, so it should not be garbage-collected, and it could be
inserted elsewhere in the DOM tree to show "yyy".

Then what about  RA.innerText = ""  which will visibly blank the DIV?
For an ordinarily naive coder, it would not be unreasonable to expect
the SPAN to still be in the DIV - and it would also not be unreasonable
to expect the SPAN to not still be in the DIV.  Neither is unreasonable;
one must be right, and one wrong.  There is still a reference to B.


The FAQ should first say something about elements, then references to
elements, then say how a DOM tree for display is grown, and can be
grafted and pruned.  It is then only necessary to say something about
the displayed properties of elements, and about the inner* methods.


See in <http://www.merlyn.demon.co.uk/js-faq-u.htm>, which does
something like that.

-- 
 (c) John Stockton, Surrey, UK.  ¬@merlyn.demon.co.uk   Turnpike v6.05   MIME.
   Web  <http://www.merlyn.demon.co.uk/> - FAQish topics, acronyms, & links.
 Proper <= 4-line sig. separator as above, a line exactly "-- " (SonOfRFC1036)
 Do not Mail News to me. Before a reply, quote with ">" or "> " (SonOfRFC1036)

[toc] | [prev] | [next] | [standalone]

#18314

In message <XBOzrxTH$EDRFwES@invalid.uk.co.demon.merlyn.invalid>, Dr J R
Stockton wrote:

  <snip>
>The FAQ should first say something about elements, then references to
>elements, then say how a DOM tree for display is grown, and can be
>grafted and pruned.  It is then only necessary to say something about
>the displayed properties of elements, and about the inner* methods.
  <snip>

There are people who think that Scientific American is too technical. I
suspect a lot of web designers are like that. They simply won't read
such a long and carefully crafted FAQ entry.

What you've suggested is tutorial material. It belongs outside the FAQ
itself.

  John
-- 
John Harris

[toc] | [prev] | [next] | [standalone]

#18331

In comp.lang.javascript message <jI$a6QFOQPDRFwTe@J.A830F0FF37FB96852AD0
8924D9443D28E23ED5CD>, Sat, 2 Feb 2013 11:10:06, John G Harris
<niam@jghnorth.org.uk.invalid> posted:

>In message <XBOzrxTH$EDRFwES@invalid.uk.co.demon.merlyn.invalid>, Dr J R
>Stockton wrote:
>
>  <snip>
>>The FAQ should first say something about elements, then references to
>>elements, then say how a DOM tree for display is grown, and can be
>>grafted and pruned.  It is then only necessary to say something about
>>the displayed properties of elements, and about the inner* methods.
>  <snip>
>
>There are people who think that Scientific American is too technical. I
>suspect a lot of web designers are like that. They simply won't read
>such a long and carefully crafted FAQ entry.
>
>What you've suggested is tutorial material. It belongs outside the FAQ
>itself.

They will not read long tutorials either.


There are existing FAQ articles longer than the above needs to be, if
links are used for details.  For the first part of the above ('*' is
used to mark a link, internal to the FAQ or external to the Notes) :-

"In a browser, a displayed Web page is represented by a tree structure
 of elements* of various types, some visible and some invisible.  An
 element is an Object* with data properties*, methods*, and pointers*,
 and is accessed using pointers referencing it.  The "DOM"* tree is
 built from the incoming HTML source.

 Elements can be created, and their properties set, by methods; and
 elements can likewise be added to and removed from the DOM tree.
 Methods are called from JavaScript* or otherwise.*"

That will no doubt benefit from tweaking; but, with care, it should not
need to get much longer.

-- 
 (c) John Stockton, nr London, UK.  Mail via homepage.  Turnpike v6.05  MIME.
  Web  <http://www.merlyn.demon.co.uk/> - FAQqish topics, acronyms and links;
  Astro stuff via astron-1.htm, gravity0.htm ; quotings.htm, pascal.htm, etc.
 No Encoding. Quotes before replies. Snip well. Write clearly. Don't Mail News.

[toc] | [prev] | [next] | [standalone]

#18334

Dr J R Stockton wrote:

> "In a browser, a displayed Web page is represented by a tree structure
>  of elements* of various types, some visible and some invisible.  An
>  element is an Object* with data properties*, methods*, and pointers*,
>  and is accessed using pointers referencing it.  The "DOM"* tree is
>  built from the incoming HTML source.
> 
>  Elements can be created, and their properties set, by methods; and
>  elements can likewise be added to and removed from the DOM tree.
>  Methods are called from JavaScript* or otherwise.*"
> 
> That will no doubt benefit from tweaking

IMO it would be more beneficial to completely rewrite it, as there's not
much truth in it.

BTW: the FAQ topic under discussion is "Why does my code fail to access
an element?", isn't it.

-- 
Christoph M. Becker

[toc] | [prev] | [next] | [standalone]

#18469

I do not know when this might be posted; my telephone line is currently
dead.


In comp.lang.javascript message <ken0vm$nl7$1@speranza.aioe.org>, Mon, 4
Feb 2013 01:56:26, Christoph Becker <cmbecker69@gmx.de> posted:

>Dr J R Stockton wrote:
>
>> "In a browser, a displayed Web page is represented by a tree structure
>>  of elements* of various types, some visible and some invisible.  An
>>  element is an Object* with data properties*, methods*, and pointers*,
>>  and is accessed using pointers referencing it.  The "DOM"* tree is
>>  built from the incoming HTML source.
>>
>>  Elements can be created, and their properties set, by methods; and
>>  elements can likewise be added to and removed from the DOM tree.
>>  Methods are called from JavaScript* or otherwise.*"
>>
>> That will no doubt benefit from tweaking
>
>IMO it would be more beneficial to completely rewrite it, as there's not
>much truth in it.

Then do so, for the public benefit.  Only constructive comment is
beneficial.

>BTW: the FAQ topic under discussion is "Why does my code fail to access
>an element?", isn't it.

It is; but it is not only the body of a FAQ topic which is discussible,
but the topic itself.  That topic can best be answered by imparting an
understanding of what may cause attempted access to an element to fail.


-- 
 (c) John Stockton, nr London, UK.   E-mail, see Home Page.    Turnpike v6.05.
 Website  <http://www.merlyn.demon.co.uk/> - w. FAQish topics, links, acronyms
 PAS EXE etc. : <http://www.merlyn.demon.co.uk/programs/> - see in 00index.htm
 Dates - miscdate.htm estrdate.htm js-dates.htm pas-time.htm critdate.htm etc.

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | comp.lang.javascript

csiph-web