New FAQ Version for review

[Randy Webb]

Re: New FAQ Version for review

RobG said the following on 11/28/2006 6:53 PM:

Randy Webb wrote:

>RobG said the following on 11/27/2006 12:20 AM:

>>Randy Webb wrote:
>>>There is an updated version of the FAQ at:
>>><URL: http://jibbering.com/faq/newfaq/>
>>[...]
>>>Thoughts and comments are welcome.
>>Can you update the CSS?

[...]

>Save the index.html and faq.css files locally, modify them and email
>them to clj...net and I can upload it and get it reviewed.

>
OK, done that.
>
Mac users (Safari users in particular) should change their monospace
font to Monaco 14pt, the default Courier (new) 13pt is way too small on
all browsers and monitors.

Check your email for an alternative email address. After checking it
from some other email addresses I don't think ctvea.net likes the file
attachments. It wouldn't even let me send myself an attachment. What a
service that is there!

--
Randy
Chance Favors The Prepared Mind
comp.lang.javas cript FAQ - http://jibbering.com/faq
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/

[RobG]

Re: New FAQ Version for review


Randy Webb wrote:
[...]

Check your email for an alternative email address. After checking it
from some other email addresses I don't think ctvea.net likes the file
attachments. It wouldn't even let me send myself an attachment. What a
service that is there!

Thanks, done that. I may not have properly attached the files.


--
Rob

[Randy Webb]

Re: New FAQ Version for review

RobG said the following on 11/28/2006 8:39 PM:

Randy Webb wrote:
[...]

>Check your email for an alternative email address. After checking it
>from some other email addresses I don't think ctvea.net likes the file
>attachments. It wouldn't even let me send myself an attachment. What a
>service that is there!

>
Thanks, done that. I may not have properly attached the files.

I am not sure it was you. I tried sending myself an email with an
attachment and the email went through but without the attachment. I have
to call them and find out what happened and why.

--
Randy
Chance Favors The Prepared Mind
comp.lang.javas cript FAQ - http://jibbering.com/faq
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/

[Randy Webb]

Re: New FAQ Version for review

Peter Michaux said the following on 11/28/2006 8:28 PM:

Randy Webb wrote:

>There is an updated version of the FAQ at:
><URL: http://jibbering.com/faq/newfaq/>

>
<snip>
>

>Thoughts and comments are welcome.

>
Below are a few.
>
Peter
>
------------
>
There seem to be two leading spaces at the start of each code example.

Fixed. I am not sure how it happened but the file that processes the XML
file was adding a leading space. The original has that leading space
added but I don't see it in the FAQ itself so not sure what is going on
with that one.

------------
>
In section 4.9
>

>When using IE6 with in CSS1Compat mode (with a Formal DOCTYPE)

>
Would this be clearer as the following?
>
When using IE6 with in CSS1Compat mode (i.e. with a Formal DOCTYPE)

Not sure but it is added.

------------
>
In section 4.13
>

>In HTML documents, named forms may be referred to as named properties of the document.forms collection

>
It seems to me that named forms are also available as properties of the
document object.

They are. But the FAQ was stressing using the FORMS collection.

------------
>
In section 4.15
>

>Using the DOM and Microsoft's innerHTML extension

>
This could be interpreted as innerHTML is only available in IE. Could
"Microsoft' s" be replaced with "the non-standard but widely
implemented"

Not sure why it was worded that way in the past, sure there was a reason
but it's modified. If there was a good reason that is still there now, I
am sure we will hear about it :)

The code example in this section seems to be for browsers without
function literals. To which browsers does this cater? Does this example
deserve updating?

What do you propose updating it to? And, what is wrong with what is
there now?

------------
>
In Section 4.18
>
The last sentance in section 4.18 could be moved to 4.44

I'm not too sure that sentence should appear at all except in 4.44 so I
moved the last sentence, along with the link, to 4.44 as an alternative
to the XMLHttpRequest Object.

------------
>
In Section 4.22
>
The function name "Random" is capitalized which is usually reserved for
constructor functions. Perhaps this should be lower case

Almost except that it uses Math.random() in the code. IIRC it was
capitalized to prevent confusion with Math.random()

The featured code in the yellow box doesn't answer the section's title
question. The actual answer is added like an after thought.

True :\

>gives a random number in the range 0..(x-1); Random(N)+1 for [1..N]

>
The range notation is not consistent in this sentence. I suggest the
use standard range notation: [1, N] and [1, N) or [1, N-1]

Modified.

------------
>
Could sections 4.25 and 4.39 should be close together or merged?

They are closely related but different. One deals with forms with []
characters in the name while the other deals with Bracket Notation in
general. Of which I have never agreed with terming it "illegal
characters" as [] are perfectly valid in HTML attributes. The problem
comes when trying to access them via script. But, it was agreed to the
wording with regards to being illegal.

The problem with merging them is historical links in the archives. Right
now I want to try to update what is there and get it live. Then it will
be time to try to go through this again with another layout/format after
there is an updated FAQ on-line.

------------
>
In Section 4.31
>
Could a mention of preloading images be added.

I have always thought it should mention it. The word "preload" nor
"pre-load" appear in the FAQ anywhere and typically when people ask
about that entry they are generally wanting to know how to preload
images. Whenever a preload entry has come up someone always beckons
about "It might not work in browser KYJ so don't do it".

The last line in that entry implies that headers are the only way to
overcome that problem and I have never seen a browser where preloading
them using new Image() didn't do the trick.

Personally, I think the whole entry needs to be retitled and re-written
as a "How do I preload images" entry along with the notes/links about
headers.

Something like
(new Image()).src = "http://example.com/maui.gif"
>
If the image is served with correct headers when this JavaScript runs
then the first time the roll over is used it won't be slow, at least in
some browsers.
>
Perhaps mentioning that sliding images can be used instead like RobG (I
believe) mentioned within the last weeks.
------------
>
In Section 4.34
>

>Mozilla, Safari, and the Windows version of IE (and Opera 7.6+)

>
I think Opera deserves to be outside of parentheses. Something like
this with the correct version numbers. (I'll research the correct
numbers if someone doesnt know off the top of their more knowing head.)

I moved the code line there to a box of it's own. Even in the old
version it starts at the end of the paragraph.

Something more like this...
>
Mozilla (NN6+, Firefox, Ice Weasle etc), Opera 7.6+, Safari, the
Windows version of IE versions 5+, and some other browsers

Updated, as you have it. If you can find version numbers for the first
level of each browser that supports it I can add the version numbers to it.


Section 4.38:

I added a link to <URL: http://www.ajaxtoolbox .comand removed the link
to Laurents Java page. In this thread:

<URL:
http://groups-beta.google.com/group/comp.lang.javas cript/browse_thread/thread/81e4f8d6ab9a4b1 7/0f859a94afc9559 8?lnk=gst&q=Lau rent+FAQ+Java&r num=1#0f859a94a fc95598>

Laurent recommended against using it so it's removed.

------------
>
In Section 4.39
>

>There are two equivalent ways to access properties

>
I suggest the removal of the word equivalent

Done. They have never been equivalent and never will :)

------------
>
In Section 4.43
>
The Firebug extension in Firefox is so valuable I think it is worth a
mention. Firebug is just going to version 1.0
>
http://www.getfirebug.com/

Added. It probably needs to be reworded but it is there.

------------
>
In Section 4.44
>
Ajax only has one capital letter. It may be an acronym but Ajax was
also a Greek God or something.
>
http://www.adaptivepath.com/publicat...ves/000385.php

Ajax has been so many things nobody is sure anymore :) But, it is changed.

Thank you.


--
Randy
Chance Favors The Prepared Mind
comp.lang.javas cript FAQ - http://jibbering.com/faq
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/

[Randy Webb]

Re: New FAQ Version for review

Dr J R Stockton said the following on 11/28/2006 7:43 AM:

In comp.lang.javas cript message <37qdnY_T3dfNiv fY4p2dnA@telcov e.net>,
Sun, 26 Nov 2006 17:39:09, Randy Webb <HikksNotAtHome @aol.comwrote:

>There is an updated version of the FAQ at:
><URL: http://jibbering.com/faq/newfaq/>

>
It (unlike 8.1) lacks a clear statement as to who maintains it.

It is added back but it didn't make a hill of beans to me so I removed
it. But, it's back in there now.

Also, it's not clear what the present status of the FAQ Notes is.
Are they still maintained?

What has indicated that they aren't?

Are they abandonware, (c) RC?
Are they detached parts of the FAQ, similarly maintained, (c)
newsgroup?

<shrug>

Do you have a proposed Notes page to add? If so, URL to it and it will
get reviewed, uploaded, and a link added to the Notes page.

IMHO, each Note should be annotated with the name of its author, its
maintainer if different, and its date;

The date, perhaps. But Author and Maintainer? The FAQ is for
information, not personal glorification.

the link to the index page should be dejargonised and repeated at the top,
and the Notes index page should enlarge a little on such matters.

What is so "jargonized " about the link and what is a proposed re-wording?

The final link at the top of Notes Index, to zipped Notes & FAQ, needs
consideration.
<FAQENTRY>FAQ section 1, or thereabouts, should contain a link to each
individual Note, as a list.
</FAQENTRY>

Why? There is already a TOC to the Notes.

If they are not now maintained, the FAQ should make that clear.

I have seen nothing to indicate they aren't maintained.

>
>

>4.20 Updated to refer to the delay in setTimeout and setInterval

>
The added sentence includes "generally" . ISTM that, for the common case
where the requested delay is a multiple of the tick interval, IE6 in
WinXP does not do that; and if IE6 (so, probably, IE7?) does not do it,
can "generally" be right?
>
The delay is not *caused* by the difference.
>
"The delay ... may exceed ... (browsers differ)."
>
>
TIDY checker reports missing <liin 4.29. Probably four are missing
(see issue 8.1, 4.29).

Fixed the LI issue. It was the result of an errant search/replace.

>
2.1 : Subject now ungrammatical.

Whatever.

>
4.12 Subject : but parseInt('09') does not give an error. It gives, as
it should, a Number of value 0.
"4.12 Why does K = parseInt('09') set K to 0?
>
Function parseInt(S, B) accepts two arguments, string S and base B; the
first character (leading whitespace excepted) in S which in that
position cannot be part of a base-B number terminates number reading.
>
If B is not given : S with leading "0x" or "0X" is read as Hexadecimal,
else S with leading "0" is read as Octal, otherwise S is read as
Decimal. Generally, it is better to use unary + : K = +S ."

I won't have this argument with you again. It has been had in the past
and when it was had you simply ducked around the argument.

N.B. When an entry's Subject is a question, the entry's body should
*always* explicitly answer that question. It should usually, but should
not only, present a solution to any implied problem. If necessary,
change the Subject.

There is nothing wrong with the Subject though.

4.16 How do I trim whitespace ...
>
String "aaa zzz" contains trimmable whitespace; but the entry ignores
that case. ASCII should read Unicode.

Proposed alternative?

>
Count : "enviroment " 3, "environmen t" 1.
>
>

>I think that 3.2 is getting sufficiently lengthy enough that it might
>benefit from being moved to a page of it's own.

>
Can one have confidence in an author who, seemingly having lived for
many years in a nominally English-speaking country, and in spite of
frequently-presented examples in this newsgroup, still apparently
believes "it's" to be a genitive? Also FAQ 4.44.

Mea bouws doun befoor yer majisty an beags fer fergiveness fer mi
transgreshuns.

NGFY

--
Randy
Chance Favors The Prepared Mind
comp.lang.javas cript FAQ - http://jibbering.com/faq
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/

[Peter Michaux]

Re: New FAQ Version for review

Hi Randy,

The code example in this section seems to be for browsers without
function literals. To which browsers does this cater? Does this example
deserve updating?

>
What do you propose updating it to? And, what is wrong with what is
there now?

It doesn't have semicolons at the ends of all the lines. I can't take
it! :S

Well maybe nothing wrong with it at all. In fact, it may work in more
browsers than with function literals. However it looks old and no one
bothers programming that way anymore, do they? Using the Function
constructor is leading in the direction of using eval where it is not
necessary.

I have no clue but I would guess that since the Function constructor
takes string arguments that it would parse the strings at run time and
be slower during execution than using a function literal which would be
parsed during compile time.

I don't know if the goal is to have getRef in the global space or not.
I doubt a closure is appropriate to this FAQ question so to keep it
looking simple for the FAQ maybe just this

var getRef,
dynWrite;

if (document.getEl ementById) {
getRef = function(id) {return document.getEle mentById(id);} ;
} else if (document.all) {
getRef = function(id) {return document.all(id );};
}

if (getRef) {
dynWrite = function(id, s) {getRef(id).inn erHTML=s; return true;};
} else {
dynWrite = function() {return false;};
}

(Can't help it, I have to remove those uppercase function names.)

I know the repetition in defining getRef could be removed but perhaps
at the cost of clarity.

Given IE 5 has getElementById isn't it time to stop all of this
document.all stuff anyway and shove those browsers down the degredation
path with NS 4 like the current example has done. In which case the
entire example becomes

var dynWrite;
if (document.getEl ementById) {
dynWrite = function(id, s) {document.getEl ementById(id).i nnerHTML=s;
return true;}
} else {
dynWrite = function(){retu rn false;}
}

This example still displays feature detection but assumes innerHTML
which is not in the character of c.l.j.

// first call to dynWrite initializes it
var dynWrite = function(id, s) {
var el;
if (document.getEl ementById &&
el = document.getEle mentById(id) &&
el.innerHTML) {
dynWrite = function(id, s) {
document.getEle mentById(id).in nerHTML=s;
return true;
}
} else {
dynWrite = function() {return false;};
}
return dynWrite(id, s);
};

Ok maybe I've gone off the deep end but if c.l.j. regulars are going to
go on about feature detection then maybe this is the necessary version.
:)

------------

In Section 4.22

The function name "Random" is capitalized which is usually reserved for
constructor functions. Perhaps this should be lower case

>
Almost except that it uses Math.random() in the code. IIRC it was
capitalized to prevent confusion with Math.random()

If lower case "random" is out then how about "chaos" or the more boring
"rand" for the function name? I really think that upper case function
names should be reserved for constructors. But hey, that's just me.

Could sections 4.25 and 4.39 should be close together or merged?

>
They are closely related but different. One deals with forms with []
characters in the name while the other deals with Bracket Notation in
general. Of which I have never agreed with terming it "illegal
characters" as [] are perfectly valid in HTML attributes. The problem
comes when trying to access them via script. But, it was agreed to the
wording with regards to being illegal.
>
The problem with merging them is historical links in the archives. Right
now I want to try to update what is there and get it live. Then it will
be time to try to go through this again with another layout/format after
there is an updated FAQ on-line.

Ok. I do think they should be close so I'll try to remember this one so
I can bring it up again and make sure the nice faq volunteer isn't
bored.

------------

In Section 4.31

Could a mention of preloading images be added.

>
I have always thought it should mention it. The word "preload" nor
"pre-load" appear in the FAQ anywhere and typically when people ask
about that entry they are generally wanting to know how to preload
images. Whenever a preload entry has come up someone always beckons
about "It might not work in browser KYJ so don't do it".
>
The last line in that entry implies that headers are the only way to
overcome that problem and I have never seen a browser where preloading
them using new Image() didn't do the trick.
>
Personally, I think the whole entry needs to be retitled and re-written
as a "How do I preload images" entry along with the notes/links about
headers.

I imagine this will be revisited later.

Mozilla, Safari, and the Windows version of IE (and Opera 7.6+)

I think Opera deserves to be outside of parentheses. Something like
this with the correct version numbers. (I'll research the correct
numbers if someone doesnt know off the top of their more knowing head.)

>
I moved the code line there to a box of it's own. Even in the old
version it starts at the end of the paragraph.
>

Something more like this...

Mozilla (NN6+, Firefox, Ice Weasle etc), Opera 7.6+, Safari, the
Windows version of IE versions 5+, and some other browsers

>
Updated, as you have it. If you can find version numbers for the first
level of each browser that supports it I can add the version numbers to it.

Randy, I'm not worth trusting for information yet, am I? I'm still just
the new kid.

I just downloaded four versions of NN6 and the first version to support
my test XHR test was 6.2

The Apple website says Safari 1.2 is the first with XHR

If someone took the time to determine Opera 7.6 was the first Opera
with XHR I believe them.

I don't know a thing about Ice Weasle except the name is hilarious and
I might not be able to stop laughing if I was using it. Especially if I
could see the Ice Weasle logo.

Perhaps the following would be appropriate

Mozilla (Netscape Navigator 6.2+, Firefox), Opera 7.6+, Safari 1.2+,
the Windows version of Internet Explorer 5+, and some other browsers.


Peter

[Randy Webb]

Re: New FAQ Version for review

Peter Michaux said the following on 11/29/2006 3:10 AM:

Hi Randy,
>

>>The code example in this section seems to be for browsers without
>>function literals. To which browsers does this cater? Does this example
>>deserve updating?

>What do you propose updating it to? And, what is wrong with what is
>there now?

>
It doesn't have semicolons at the ends of all the lines. I can't take
it! :S

Ahhh, the semicolons... :)

<snip>

Given IE 5 has getElementById isn't it time to stop all of this
document.all stuff anyway and shove those browsers down the degredation
path with NS 4 like the current example has done. In which case the
entire example becomes

If IE4 support is dropped then the entire entry answer becomes
document.getEle mentById(yourEl ementId).innerH TML = newHTML;

Does it not? And I didn't think IE4 needed to be covered even when NN4
was dropped and definitely don't think it should be included now. People
using IE4 now can't use 90% of the web anyway so not a lot in the FAQ is
of much use to them for any reason other than historical reasons.

Ok maybe I've gone off the deep end but if c.l.j. regulars are going to
go on about feature detection then maybe this is the necessary version.
:)

if (document &&
document.getEle mentById &&
document.getEle mentById('someE lement') &&
document.getEle mentById('someE lement').innerH TML)
{
document.getEle mentById(someEl ement').innerHT ML = "some HTML here"
}

>>------------
>>>
>>In Section 4.22
>>>
>>The function name "Random" is capitalized which is usually reserved for
>>constructor functions. Perhaps this should be lower case

>Almost except that it uses Math.random() in the code. IIRC it was
>capitalized to prevent confusion with Math.random()

>
If lower case "random" is out then how about "chaos" or the more boring
"rand" for the function name? I really think that upper case function
names should be reserved for constructors. But hey, that's just me.

It is so widely known that there isn't really any benefit in changing
it. Maybe randomNumber(x) .

<snip>

>>------------
>>>
>>In Section 4.31
>>>
>>Could a mention of preloading images be added.

>I have always thought it should mention it. The word "preload" nor
>"pre-load" appear in the FAQ anywhere and typically when people ask
>about that entry they are generally wanting to know how to preload
>images. Whenever a preload entry has come up someone always beckons
>about "It might not work in browser KYJ so don't do it".
>>
>The last line in that entry implies that headers are the only way to
>overcome that problem and I have never seen a browser where preloading
>them using new Image() didn't do the trick.
>>
>Personally, I think the whole entry needs to be retitled and re-written
>as a "How do I preload images" entry along with the notes/links about
>headers.

>
I imagine this will be revisited later.

Absolutely. Preloading seems to come up pretty often. Either directly or
indirectly but I don't recall seeing any one post and ask "Why are my
rollovers so slow?"

>>>Mozilla, Safari, and the Windows version of IE (and Opera 7.6+)
>>I think Opera deserves to be outside of parentheses. Something like
>>this with the correct version numbers. (I'll research the correct
>>numbers if someone doesnt know off the top of their more knowing head.)

>I moved the code line there to a box of it's own. Even in the old
>version it starts at the end of the paragraph.
>>

>>Something more like this...
>>>
>>Mozilla (NN6+, Firefox, Ice Weasle etc), Opera 7.6+, Safari, the
>>Windows version of IE versions 5+, and some other browsers

>Updated, as you have it. If you can find version numbers for the first
>level of each browser that supports it I can add the version numbers to it.

>
Randy, I'm not worth trusting for information yet, am I? I'm still just
the new kid.

If you are downloading and installing browsers then why would anybody
have a reason not to believe you until you give them a reason? I tend to
give people some benefit unless they are posting questions that can be
answered in 30 seconds in the archives, then I get my typically ranting
attitude.

I just downloaded four versions of NN6 and the first version to support
my test XHR test was 6.2
>
The Apple website says Safari 1.2 is the first with XHR
>
If someone took the time to determine Opera 7.6 was the first Opera
with XHR I believe them.
>
I don't know a thing about Ice Weasle except the name is hilarious and
I might not be able to stop laughing if I was using it. Especially if I
could see the Ice Weasle logo.

<URL: http://www.gnu.org/software/gnuzilla/>

He's kinda cute actually.....

Perhaps the following would be appropriate
>
Mozilla (Netscape Navigator 6.2+, Firefox), Opera 7.6+, Safari 1.2+,
the Windows version of Internet Explorer 5+, and some other browsers.

I left the name Ice Weasel in it because it's a Debian browser which is
a different OS but it's based on Mozilla. From what I have read about it
though, it is simply Firefox for the Debian Package with a different
name/logo.

--
Randy
Chance Favors The Prepared Mind
comp.lang.javas cript FAQ - http://jibbering.com/faq
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/

[Dr J R Stockton]

Re: New FAQ Version for review

In comp.lang.javas cript message
<ekftep$16q$1$8 302bc10@news.de mon.co.uk>, Mon, 27 Nov 2006 23:36:42,
Richard Cornford <Richard@litote s.demon.co.ukwr ote:

>Randy Webb wrote:

>Richard Cornford said the following on 11/26/2006 6:51 PM:

>>Randy Webb wrote:

><snip>

>>I never thought that there was anything wrong with the
>>wording of 4.13 as it was,

>>
>The wording, as it was, implied there was One exception,
>then it says there is another exception.

><snip>
>
>No it did not. It gave two examples of exceptions form an indefinite
>set.

We cannot expect a Merkin to be able to understand English.

By "One exception ..." ... "Another exception ..." you clearly suggested
that at least one other exception was possible or likely or certain.

Randy asserts that there are exactly three exceptions - which is
egg-on-his-face if anyone demonstrates another,


But, you being a Failed FAQ writer, it ill behoves you to criticise one
who is at least trying.

It's a good idea to read the newsgroup and its old FAQ. See below.

--
(c) John Stockton, Surrey, UK. ?@merlyn.demon. co.uk Turnpike v6.05 IE 6
<URL:http://www.jibbering.c om/faq/ Old RC FAQ of news:comp.lang. javascript
<URL:http://www.merlyn.demo n.co.uk/js-index.htmjscr maths, dates, sources.
<URL:http://www.merlyn.demo n.co.uk/TP/BP/Delphi/jscr/&c, FAQ items, links.

[Dr J R Stockton]

Re: New FAQ Version for review

In comp.lang.javas cript message <H6idnd1cWKr7hf DY4p2dnA@telcov e.net>,
Wed, 29 Nov 2006 00:19:38, Randy Webb <HikksNotAtHome @aol.comwrote:

>Dr J R Stockton said the following on 11/28/2006 7:43 AM:

>In comp.lang.javas cript message <37qdnY_T3dfNiv fY4p2dnA@telcov e.net>,
>Sun, 26 Nov 2006 17:39:09, Randy Webb <HikksNotAtHome @aol.comwrote:

>>There is an updated version of the FAQ at:
>><URL: http://jibbering.com/faq/newfaq/>

> It (unlike 8.1) lacks a clear statement as to who maintains it.

>
>It is added back but it didn't make a hill of beans to me so I removed
>it. But, it's back in there now.
>

>Also, it's not clear what the present status of the FAQ Notes is.
> Are they still maintained?

>
>What has indicated that they aren't?

What has indicated that they are?

> Are they abandonware, (c) RC?
> Are they detached parts of the FAQ, similarly maintained, (c)
>newsgroup?

>
><shrug>
>
>Do you have a proposed Notes page to add? If so, URL to it and it will
>get reviewed, uploaded, and a link added to the Notes page.
>

>IMHO, each Note should be annotated with the name of its author, its
>maintainer if different, and its date;

>
>The date, perhaps. But Author and Maintainer? The FAQ is for
>information, not personal glorification.

An author should be prepared to put his name to his work, and to receive
comment both favourable and unfavourable.

>the link to the index page should be dejargonised and repeated at the
>>top, and the Notes index page should enlarge a little on such
>>matters.

>
>What is so "jargonized " about the link and what is a proposed re-wording?
>

>The final link at the top of Notes Index, to zipped Notes & FAQ,
>>needs consideration.
><FAQENTRY>FA Q section 1, or thereabouts, should contain a link to each
>individual Note, as a list.
></FAQENTRY>

>
>Why? There is already a TOC to the Notes.

Because we do not all have continuous access to the Net/Web, but those
of us who have sensibly chosen our News access method do, when using our
computers, have permanent access to the FAQ as posted to News.

>If they are not now maintained, the FAQ should make that clear.

>
>I have seen nothing to indicate they aren't maintained.

I have seen nothing to indicate that they are.

> 2.1 : Subject now ungrammatical.

>
>Whatever.

Even the weakest knowledge of English grammar should suffice to tell
that the change is to an error. The plural noun requires a plural verb
form here. It is a change (in falsely-dated 9.0) from 8.1.

> 4.12 Subject : but parseInt('09') does not give an error. It gives,
>>as
>it should, a Number of value 0.
>"4.12 Why does K = parseInt('09') set K to 0?
> Function parseInt(S, B) accepts two arguments, string S and base B;
>>the
>first character (leading whitespace excepted) in S which in that
>position cannot be part of a base-B number terminates number reading.
> If B is not given : S with leading "0x" or "0X" is read as
>>Hexadecimal ,
>else S with leading "0" is read as Octal, otherwise S is read as
>Decimal. Generally, it is better to use unary + : K = +S ."

>
>I won't have this argument with you again. It has been had in the past
>and when it was had you simply ducked around the argument.

I don't recall arguing about whether parseInt("09") gives an error. It
gives Number 0, as is right and proper. The newsgroup regulars are in
general agreement, ISTM, that unary + is good.

>N.B. When an entry's Subject is a question, the entry's body should
>*always* explicitly answer that question. It should usually, but should
>not only, present a solution to any implied problem. If necessary,
>change the Subject.

>
>There is nothing wrong with the Subject though.

Eh? "*The* Subject"? That is a general remark, applying to all entries
in S.4.

The present Subject of 4.12 is wrong in that no error is given (though
the result may not match what was wanted). For a complete response to
the "Why" one must state that the first character which cannot be part
of the number causes termination, so that "09" is treated as "0" which
is then read /* in octal */ and yields Number 0.

>4.16 How do I trim whitespace ...
> String "aaa zzz" contains trimmable whitespace; but the entry
>>ignores
>that case. ASCII should read Unicode.

>
>Proposed alternative?

If you cannot write, at full speed, a .Replace() using a RegExp to
reduce multiple embedded whitespace to a single space, then see any
tutorial on RegExps. The non-RegExp part of 4.16 is no longer worth
keeping.

BTW, the FAQ lacks a general RegExps section. Such a section should not
be long, but should refer to their great utility and provide a couple of
links. You should know where to look for a longer treatment.


--
(c) John Stockton, Surrey, UK. ?@merlyn.demon. co.uk Turnpike v6.05 MIME.
<URL:http://www.merlyn.demo n.co.uk/TP/BP/Delphi/&c., FAQqy topics & links;
<URL:http://www.merlyn.demo n.co.uk/clpb-faq.txt RAH Prins : c.l.p.b mFAQ;
<URL:ftp://garbo.uwasa.fi/pc/link/tsfaqp.zipTimo Salmi's Turbo Pascal FAQ.

[Dr J R Stockton]

Re: New FAQ Version for review

In comp.lang.javas cript message <pvCdnc-RhZkd0PDY4p2dnA @telcove.net>,
Wed, 29 Nov 2006 04:06:09, Randy Webb <HikksNotAtHome @aol.comwrote:

>

>Given IE 5 has getElementById isn't it time to stop all of this
>document.all stuff anyway and shove those browsers down the degredation
>path with NS 4 like the current example has done. In which case the
>entire example becomes

>
>If IE4 support is dropped then the entire entry answer becomes
>document.getEl ementById(yourE lementId).inner HTML = newHTML;
>
>Does it not? And I didn't think IE4 needed to be covered even when NN4
>was dropped and definitely don't think it should be included now.
>People using IE4 now can't use 90% of the web anyway so not a lot in
>the FAQ is of much use to them for any reason other than historical
>reasons.

Well, 99% of the Web is rubbish, blatantly commercial, or both. But, of
the rest, over 95% of what I wanted to see was accessible to IE4.

Those who write pages for use by impoverished organisations, maybe in
the Third World, may still want to support older systems.

And one must not fall into the same trap as a certain computer supplier,
whose Web site (including order-placing part) was only accessible to
those with computers too new to need replacing.

However, the code cited above lacks one advantage of DynWrite : it is,
wherever used, longer.

function DineRite(ID, HTML) {
document.getEle mentById(ID).in nerHTML = HTML }

is the way to go, so that in the code one sees the job each time and not
the mechanism.

--
(c) John Stockton, Surrey, UK. ?@merlyn.demon. co.uk Turnpike v6.05 MIME.
Web <URL:http://www.merlyn.demo n.co.uk/- FAQish topics, acronyms, & links.
For news:borland.*, use their server newsgroups.borl and.com ; but first read
Guidelines <URL:http://www.borland.com/newsgroups/guide.htmlff. with care.

[Richard Cornford]

Re: New FAQ Version for review

Dr J R Stockton wrote:

Richard Cornford wrote:

>>Randy Webb wrote:

>>Richard Cornford said the following on 11/26/2006 6:51 PM:
>>>Randy Webb wrote:

>><snip>

>>>I never thought that there was anything wrong with the
>>>wording of 4.13 as it was,
>>>
>>The wording, as it was, implied there was One exception,
>>then it says there is another exception.

>><snip>
>>
>No it did not. It gave two examples of exceptions form an
>indefinite set.

>
We cannot expect a Merkin to be able to understand English.

That would you depend on what you mean by "Murkin". My dictionary says;
"a hairpiece for the pubic area. [Origin uncertain]". If I had been
aware of their existence I would not have expected them to understand
English.

I do expect citizens of the United States to understand English. I may
yet be disappointed but those I have conversed with to date don't seem
to have any serious difficulty doing so.

By "One exception ..." ... "Another exception ..." you

Mike Winter wrote the wording for that version of that entry.

clearly suggested that at least one other exception was
possible or likely or certain.
>
Randy asserts that there are exactly three exceptions -
which is egg-on-his-face if anyone demonstrates another,

Any attempt to list all risks becoming extended. I seem to recall some
early Opera versions asking the user for permission to allow scripts to
access <input type="password" fields (I don't know why as if
cross-domain scripting is properly excluded that should not be a
security issue).

But, you being a Failed FAQ writer, it ill behoves you to
criticise one who is at least trying.

<snip>

I was not criticising Randy. I was hoping he might ask for a second
opinion on his interpretation, as I suspect that the first 5 people he
asked would reveal a majority in favour of my interpretation.

Richard.

[Randy Webb]

Re: New FAQ Version for review

Richard Cornford said the following on 11/29/2006 8:01 PM:

Dr J R Stockton wrote:

<snip>

>By "One exception ..." ... "Another exception ..." you

>
Mike Winter wrote the wording for that version of that entry.

The wording just seemed odd to me was all. Might have just been me
<shrug>. With a third exception being file inputs, would it be better to
change it to something like this:

Some exceptions would be:

Or, is the list sufficient enough to move it a Notes section?

--
Randy
Chance Favors The Prepared Mind
comp.lang.javas cript FAQ - http://jibbering.com/faq
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/

[Randy Webb]

Re: New FAQ Version for review

Dr J R Stockton said the following on 11/29/2006 6:51 PM:

In comp.lang.javas cript message <pvCdnc-RhZkd0PDY4p2dnA @telcove.net>,
Wed, 29 Nov 2006 04:06:09, Randy Webb <HikksNotAtHome @aol.comwrote:

>>Given IE 5 has getElementById isn't it time to stop all of this
>>document.al l stuff anyway and shove those browsers down the degredation
>>path with NS 4 like the current example has done. In which case the
>>entire example becomes

>If IE4 support is dropped then the entire entry answer becomes
>document.getEl ementById(yourE lementId).inner HTML = newHTML;
>>
>Does it not? And I didn't think IE4 needed to be covered even when NN4
>was dropped and definitely don't think it should be included now.
>People using IE4 now can't use 90% of the web anyway so not a lot in
>the FAQ is of much use to them for any reason other than historical
>reasons.

>
Well, 99% of the Web is rubbish, blatantly commercial, or both. But, of
the rest, over 95% of what I wanted to see was accessible to IE4.

I said nothing about your personal browsing habits. I said they can't
use 90% of the web.

Those who write pages for use by impoverished organisations, maybe in
the Third World, may still want to support older systems.

Then let them search the archives or ask how to support an older system.
By that reasoning, the FAQ entry should cover NN4 as well......

However, the code cited above lacks one advantage of DynWrite : it is,
wherever used, longer.
>
function DineRite(ID, HTML) {
document.getEle mentById(ID).in nerHTML = HTML }
>
is the way to go, so that in the code one sees the job each time and not
the mechanism.

That one is shorter but it suffers a flaw that my code dosen't.

--
Randy
Chance Favors The Prepared Mind
comp.lang.javas cript FAQ - http://jibbering.com/faq
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/

[Randy Webb]

Re: New FAQ Version for review

Dr J R Stockton said the following on 11/28/2006 3:01 PM:

In comp.lang.javas cript message
<ekftep$16q$1$8 302bc10@news.de mon.co.uk>, Mon, 27 Nov 2006 23:36:42,
Richard Cornford <Richard@litote s.demon.co.ukwr ote:

>Randy Webb wrote:

>>Richard Cornford said the following on 11/26/2006 6:51 PM:
>>>Randy Webb wrote:

><snip>

>>>I never thought that there was anything wrong with the
>>>wording of 4.13 as it was,
>>>
>>The wording, as it was, implied there was One exception,
>>then it says there is another exception.

><snip>
>>
>No it did not. It gave two examples of exceptions form an indefinite
>set.

>
We cannot expect a Merkin to be able to understand English.
>
By "One exception ..." ... "Another exception ..." you clearly suggested
that at least one other exception was possible or likely or certain.
Randy asserts that there are exactly three exceptions - which is
egg-on-his-face if anyone demonstrates another,

No. The entry doesn't say "The only three exceptions are.." It said
"Three exceptions are". I thought you would realize that but evidently
your hatred of anything American is clouding your judgement.

But, you being a Failed FAQ writer, it ill behoves you to criticise one
who is at least trying.

Richard is far from a "Failed FAQ writer". To date, Richard has written
approximately 10 kazillion times as much in the FAQ as you have. All I
have seen you do is post about once a week requesting something be added
yet I have seen only one or two posts where you actually offer any kind
of proposed entry. It is typically you just whining about nothing
getting done. Well, not a lot can get done when either Richard or myself
has to spend time weeding through your non-productive FAQ requests in
order to get something done. Maybe you should check the post from Peter
and use it as a guideline to future requests.

--
Randy
Chance Favors The Prepared Mind
comp.lang.javas cript FAQ - http://jibbering.com/faq
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/

[Randy Webb]

Re: New FAQ Version for review

Dr J R Stockton said the following on 11/29/2006 6:23 PM:

In comp.lang.javas cript message <H6idnd1cWKr7hf DY4p2dnA@telcov e.net>,
Wed, 29 Nov 2006 00:19:38, Randy Webb <HikksNotAtHome @aol.comwrote:

>Dr J R Stockton said the following on 11/28/2006 7:43 AM:

>>In comp.lang.javas cript message <37qdnY_T3dfNiv fY4p2dnA@telcov e.net>,
>>Sun, 26 Nov 2006 17:39:09, Randy Webb <HikksNotAtHome @aol.comwrote:
>>>There is an updated version of the FAQ at:
>>><URL: http://jibbering.com/faq/newfaq/>
>> It (unlike 8.1) lacks a clear statement as to who maintains it.

>>
>It is added back but it didn't make a hill of beans to me so I removed
>it. But, it's back in there now.
>>

>>Also, it's not clear what the present status of the FAQ Notes is.
>> Are they still maintained?

>>
>What has indicated that they aren't?

>
What has indicated that they are?

You are one of the most evasive people I have ever tried to have a
conversation with. The Notes section is maintained. There is nothing to
indicate they aren't. If you have some solid reasonable reason for
thinking they aren't then please state it. If you intend to continue to
be evasive about it then please drop it.

<snip>

>>IMHO, each Note should be annotated with the name of its author, its
>>maintainer if different, and its date;

>>
>The date, perhaps. But Author and Maintainer? The FAQ is for
>information, not personal glorification.

>
An author should be prepared to put his name to his work, and to receive
comment both favourable and unfavourable.

You don't need an author's name to comment about code. The only reason
for wanting a name is to critique the person. Second, any code in the
FAQ or Notes can't easily be changed by the person writing it. If there
is a problem with code in either the FAQ or the Notes then only three
people - to the best of my knowledge - have the ability and access to
change it. Directing comments to the author becomes moot. In short - I
am not inclined to go through and comment who wrote what code in the FAQ
or the Notes pages.

>>The final link at the top of Notes Index, to zipped Notes & FAQ,
>>needs consideration.
>><FAQENTRY>F AQ section 1, or thereabouts, should contain a link to each
>>individual Note, as a list.
>></FAQENTRY>

I won't comment on the wisdom of putting an FAQENTRY marker in a
conversation that is being conducted in a thread directly addressing
updating the FAQ and especially when the conversation is being conducted
with the person that would be reacting to that FAQENTRY request.

>Why? There is already a TOC to the Notes.

>
Because we do not all have continuous access to the Net/Web, but those
of us who have sensibly chosen our News access method do, when using our
computers, have permanent access to the FAQ as posted to News.

I am not going to change the TOC to the Notes to satisfy your wants and
desires based on you not being connected at all times. If you want "easy
access" to the Notes then do it the same way you have access to the FAQ.
Download the .zip file, unzip it, and you have total 100% access to them.

>> 4.12 Subject : but parseInt('09') does not give an error. It gives, as
>>it should, a Number of value 0.
>>"4.12 Why does K = parseInt('09') set K to 0?
>> Function parseInt(S, B) accepts two arguments, string S and base B; the
>>first character (leading whitespace excepted) in S which in that
>>position cannot be part of a base-B number terminates number reading.
>> If B is not given : S with leading "0x" or "0X" is read as Hexadecimal,
>>else S with leading "0" is read as Octal, otherwise S is read as
>>Decimal. Generally, it is better to use unary + : K = +S ."

>>
>I won't have this argument with you again. It has been had in the past
>and when it was had you simply ducked around the argument.

>
I don't recall arguing about whether parseInt("09") gives an error. It
gives Number 0, as is right and proper. The newsgroup regulars are in
general agreement, ISTM, that unary + is good.

Then what is your proposed re-wording of the Subject of 4.12?

>>N.B. When an entry's Subject is a question, the entry's body should
>>*always* explicitly answer that question. It should usually, but should
>>not only, present a solution to any implied problem. If necessary,
>>change the Subject.

>>
>There is nothing wrong with the Subject though.

>
Eh? "*The* Subject"? That is a general remark, applying to all entries
in S.4.

No it wasn't, but believe what you want.

>>4.16 How do I trim whitespace ...
>> String "aaa zzz" contains trimmable whitespace; but the entry ignores
>>that case. ASCII should read Unicode.

>>
>Proposed alternative?

>
If you cannot write, at full speed, a .Replace() using a RegExp to
reduce multiple embedded whitespace to a single space, then see any
tutorial on RegExps. The non-RegExp part of 4.16 is no longer worth
keeping.

Once again, you want something changed but you don't want to propose an
alternative?

--
Randy
Chance Favors The Prepared Mind
comp.lang.javas cript FAQ - http://jibbering.com/faq
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/